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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-admin by date

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