From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gaetano Mendola <mendola@bigfoot.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Single table vacuum full different when vacuum full the whole database
Date: Sun, 17 Oct 2004 20:39:11 -0400
Message-ID: <15105.1098059951@sss.pgh.pa.us> (raw)
In-Reply-To: <417309C0.4020100@bigfoot.com>
References: <417309C0.4020100@bigfoot.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, mendola@bigfoot.com
Subject: Re: Single table vacuum full different when vacuum full the whole database
In-Reply-To: <15105.1098059951@sss.pgh.pa.us>
References: <417309C0.4020100@bigfoot.com> <15105.1098059951@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox