Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: Single table vacuum full different when vacuum full the whole database
Date
Msg-id 15105.1098059951@sss.pgh.pa.us
Whole thread Raw
In response to Single table vacuum full different when vacuum full the whole database  (Gaetano Mendola <mendola@bigfoot.com>)
Responses Re: Single table vacuum full different when vacuum full the whole  (Gaetano Mendola <mendola@bigfoot.com>)
List pgsql-admin
Tree view 
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 ...

            regards, tom lane

pgsql-admin by date:

Previous
From: Gaetano Mendola
Date:
Subject: Single table vacuum full different when vacuum full the whole database
Next
From: Gaetano Mendola
Date:
Subject: Re: Single table vacuum full different when vacuum full the whole