<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>VACUUM ANALYZE &#8211; Database Research &amp; Development</title>
	<atom:link href="https://www.dbrnd.com/tag/vacuum-analyze/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dbrnd.com</link>
	<description>BIGData &#124; NoSQL &#124; MSSQL &#124; MySQL &#124; PostgreSQL</description>
	<lastBuildDate>Tue, 10 Apr 2018 20:08:51 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.6</generator>
	<item>
		<title>PostgreSQL: VACUUM VERBOSE to find data pages and dead row versions</title>
		<link>https://www.dbrnd.com/2018/04/postgresql-vacuum-verbose-to-find-data-pages-and-dead-row-versions/</link>
		
		<dc:creator><![CDATA[Anvesh Patel]]></dc:creator>
		<pubDate>Fri, 13 Apr 2018 16:16:22 +0000</pubDate>
				<category><![CDATA[PostgreSQL]]></category>
		<category><![CDATA[Anvesh Patel]]></category>
		<category><![CDATA[data pages]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[database research and development]]></category>
		<category><![CDATA[dbrnd]]></category>
		<category><![CDATA[dead rows]]></category>
		<category><![CDATA[Multiversion Concurrency Control]]></category>
		<category><![CDATA[MVCC]]></category>
		<category><![CDATA[plpgsql]]></category>
		<category><![CDATA[Postgres Query]]></category>
		<category><![CDATA[postgresql]]></category>
		<category><![CDATA[PostgreSQL Administrator]]></category>
		<category><![CDATA[PostgreSQL Error]]></category>
		<category><![CDATA[PostgreSQL Programming]]></category>
		<category><![CDATA[PostgreSQL Tips and Tricks]]></category>
		<category><![CDATA[VACUUM ANALYZE]]></category>
		<category><![CDATA[VACUUM VERBOSE]]></category>
		<category><![CDATA[VACUUM VERBOSE ANALYZE]]></category>
		<guid isPermaLink="false">https://www.dbrnd.com/?p=4290</guid>

					<description><![CDATA[If you don&#8217;t know about that data pages, you must visit below article. What is MVCC ? Because of MVCC architecture, PostgreSQL generates dead rows at every UPDATE and DELETE. You must remove the fragmentation by executing VACUUM ANALYZE command which removes the dead rows and update the related database statistics. You can also use [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2018%2F04%2Fpostgresql-vacuum-verbose-to-find-data-pages-and-dead-row-versions%2F&amp;linkname=PostgreSQL%3A%20VACUUM%20VERBOSE%20to%20find%20data%20pages%20and%20dead%20row%20versions" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2018%2F04%2Fpostgresql-vacuum-verbose-to-find-data-pages-and-dead-row-versions%2F&amp;linkname=PostgreSQL%3A%20VACUUM%20VERBOSE%20to%20find%20data%20pages%20and%20dead%20row%20versions" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2018%2F04%2Fpostgresql-vacuum-verbose-to-find-data-pages-and-dead-row-versions%2F&amp;linkname=PostgreSQL%3A%20VACUUM%20VERBOSE%20to%20find%20data%20pages%20and%20dead%20row%20versions" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_pinterest" href="https://www.addtoany.com/add_to/pinterest?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2018%2F04%2Fpostgresql-vacuum-verbose-to-find-data-pages-and-dead-row-versions%2F&amp;linkname=PostgreSQL%3A%20VACUUM%20VERBOSE%20to%20find%20data%20pages%20and%20dead%20row%20versions" title="Pinterest" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2018%2F04%2Fpostgresql-vacuum-verbose-to-find-data-pages-and-dead-row-versions%2F&amp;linkname=PostgreSQL%3A%20VACUUM%20VERBOSE%20to%20find%20data%20pages%20and%20dead%20row%20versions" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_pocket" href="https://www.addtoany.com/add_to/pocket?linkurl=https%3A%2F%2Fwww.dbrnd.com%2F2018%2F04%2Fpostgresql-vacuum-verbose-to-find-data-pages-and-dead-row-versions%2F&amp;linkname=PostgreSQL%3A%20VACUUM%20VERBOSE%20to%20find%20data%20pages%20and%20dead%20row%20versions" title="Pocket" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share#url=https%3A%2F%2Fwww.dbrnd.com%2F2018%2F04%2Fpostgresql-vacuum-verbose-to-find-data-pages-and-dead-row-versions%2F&#038;title=PostgreSQL%3A%20VACUUM%20VERBOSE%20to%20find%20data%20pages%20and%20dead%20row%20versions" data-a2a-url="https://www.dbrnd.com/2018/04/postgresql-vacuum-verbose-to-find-data-pages-and-dead-row-versions/" data-a2a-title="PostgreSQL: VACUUM VERBOSE to find data pages and dead row versions"></a></p><p>If you don&#8217;t know about that data pages, you must visit below article.<br />
<a href="https://www.dbrnd.com/2015/05/what-is-mvcc-multi-version-concurrency-control/" target="_blank">What is MVCC ?</a></p>
<p>Because of MVCC architecture, PostgreSQL generates dead rows at every UPDATE and DELETE. </p>
<p>You must remove the fragmentation by executing VACUUM ANALYZE command which removes the dead rows and update the related database statistics. </p>
<blockquote><p>You can also use VACUUM VERBOSE to troubleshoot total number of data pages, total number of removable dead row version while executing a VACUUM ANALYZE.<br />
(Check your query message window, where you can find detailed information generated by VACUUM VERBOSE.)</p>
<p>This is really very helpful information for PostgreSQL DBA to make sure about the fragmentation. </p></blockquote>
<p>I have prepared a detailed demonstration of this.</p>
<p><strong>Create a table with sample data:</strong></p>
<pre class="crayon-plain-tag">CREATE TABLE tbl_ItemTransactions 
 (
     TranID SERIAL
     ,TransactionDate TIMESTAMPTZ
     ,TransactionName TEXT
 ) DISTRIBUTED BY (TranID);

INSERT INTO tbl_ItemTransactions 
(TransactionDate, TransactionName)
SELECT x, 'ggkproduct' 
FROM generate_series('2015-01-01 00:00:00'::timestamptz, '2016-08-01 00:00:00'::timestamptz,'5 seconds'::interval) a(x);</pre> </p>
<p><strong>Check the size of table:</strong></p>
<pre class="crayon-plain-tag">SELECT pg_size_pretty(pg_total_relation_size('tbl_ItemTransactions')) AS TableSize;

The size is: "496 MB"</pre> </p>
<p><strong>Execute VACUUM VERBOSE to get data pages and dead row versions related information:</strong></p>
<pre class="crayon-plain-tag">VACUUM VERBOSE ANALYZE tbl_ItemTransactions;

"tbl_itemtransactions": found 0 removable, 2496960 nonremovable row versions in 3970 pages  (seg0 sdw1:40000 pid=17647)</pre> </p>
<p><strong>Execute one DELETE to generate few dead tuples:</strong></p>
<pre class="crayon-plain-tag">DELETE FROM tbl_ItemTransactions 
WHERE TransactionDate BETWEEN '2016-04-01' AND '2016-08-01';</pre> </p>
<p><strong>Now, examine the result of VACUUM VERBOSE where you can find 527040 removable rows:</strong><br />
You can find total 3970 pages and 527040 removable rows.</p>
<pre class="crayon-plain-tag">VACUUM VERBOSE ANALYZE tbl_ItemTransactions;

INFO:  "tbl_itemtransactions": found 527040 removable, 1969920 nonremovable row versions in 3970 pages  (seg1 sdw1:40001 pid=17649)
839 pages contain useful free space.</pre> </p>
<p><strong>Now, execute one more time and you can find 3132 pages and 0 removable rows:</strong></p>
<pre class="crayon-plain-tag">VACUUM VERBOSE ANALYZE tbl_ItemTransactions;

"tbl_itemtransactions": found 0 removable, 1969920 nonremovable row versions in 3132 pages  (seg0 sdw1:40000 pid=17647)
1 pages contain useful free space.</pre> </p>
<p><strong>Check the size of table:</strong></p>
<pre class="crayon-plain-tag">SELECT pg_size_pretty(pg_total_relation_size('tbl_ItemTransactions')) AS TableSize;

The size is: "392 MB"</pre> </p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
