From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris Hoover <revoohc@sermonaudio.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum questions
Date: Wed, 16 Mar 2005 02:27:48 -0500
Message-ID: <3243.1110958068@sss.pgh.pa.us> (raw)
In-Reply-To: <423749C1.2030803@sermonaudio.com>
References: <423749C1.2030803@sermonaudio.com>
"Chris Hoover" <revoohc@sermonaudio.com> writes:
> We have also had one test occurrence where after the upgrade, a vacuum
> full would not recover the space. However, when we bounced the
> postmaster, and then performed a vacuum full, the space was recovered.
> Any ideas on what might cause this?
Most likely, you had an open transaction lurking that was old enough
that it could still "see" the deleted data, and so VACUUM couldn't
safely reclaim the data.
VACUUM's decisions about this are cluster-wide; so even though you'd
recently created the database in question, a long-running transaction
in another database under the same postmaster could still cause the
problem.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, revoohc@sermonaudio.com
Subject: Re: Vacuum questions
In-Reply-To: <3243.1110958068@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