From: Tom Lane <tgl@sss.pgh.pa.us>
To: Eamonn Kent <ekent@xsigo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Vacuum not identifying rows for removal..
Date: Mon, 21 Aug 2006 17:06:28 -0400
Message-ID: <19272.1156194388@sss.pgh.pa.us> (raw)
In-Reply-To: <9146E3EBBFBCC94D95F95A1C4065348A837AB1@exch01.xsigo.com>
References: <9146E3EBBFBCC94D95F95A1C4065348A837AB1@exch01.xsigo.com>
"Eamonn Kent" <ekent@xsigo.com> writes:
> I am using PostgreSQL 8.1.4 for an embedded application. For some
> reason, vacuum is not able to identify rows that are candidates for
> removal (i.e., mark space as available).
> ...
> We run auto vacuum and I can see from the logs that it is running quite
> frequently. When I run vacuum full from the psql, I can see that space
> is not being recovered. I have run vacuum full with the verbose flag
> set, I can see that messages that indicate the existence of "dead row
> versions that cannot be removed yet.
This means you've got an open transaction somewhere that could
potentially still be able to see those rows. Look around for
applications sitting "idle in transaction".
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, ekent@xsigo.com
Subject: Re: Vacuum not identifying rows for removal..
In-Reply-To: <19272.1156194388@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