Skip site navigation (1) Skip section navigation (2)

Re: Single table vacuum full different when vacuum full the whole database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gaetano Mendola <mendola(at)bigfoot(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Single table vacuum full different when vacuum full the whole database
Date: 2004-10-18 00:39:11
Message-ID: 15105.1098059951@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
Gaetano Mendola <mendola(at)bigfoot(dot)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

In response to

Responses

pgsql-admin by date

Next:From: Gaetano MendolaDate: 2004-10-18 00:49:52
Subject: Re: Single table vacuum full different when vacuum full the whole
Previous:From: Gaetano MendolaDate: 2004-10-18 00:09:36
Subject: Single table vacuum full different when vacuum full the whole database

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group