Postgres Pro
Downloads
Home   >   mailing lists

Re: Single table vacuum full different when vacuum full the whole - Mailing list pgsql-admin

From Gaetano Mendola
Subject Re: Single table vacuum full different when vacuum full the whole
Date
Msg-id 41731330.9090105@bigfoot.com
Whole thread Raw
In response to Re: Single table vacuum full different when vacuum full the whole database  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Tree view 
Tom Lane wrote:> Gaetano Mendola <mendola@bigfoot.com> writes:>>>it seems that a vacuum full on the whole DB is more
aggressive.>>>It is not.>> A much more plausible theory is that this is the result of concurrent> changes to the table.
It is clear from the "dead row versions" stats> that there were concurrent transactions ... 

That is the more updated/inserted table, and yes there were some concurrent
transaction but, is it plausible that 82 dead rows were responsible of grab
26000 index row:

INFO:  index "ua_user_data_exp_id_user_key" now contains 34438 row versions in 886 pages
DETAIL:  27488 index row versions were removed.

instead of:

INFO:  index "ua_user_data_exp_id_user_key" now contains 34519 row versions in 886 pages
DETAIL:  1362 index row versions were removed.





Regards
Gaetano Mendola

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Single table vacuum full different when vacuum full the whole database
Next
From: Bruce Momjian
Date:
Subject: Re: set AUTOCOMMIT OFF in psqlrc not having affect