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

Re: Vacuum not identifying rows for removal..

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Eamonn Kent" <ekent(at)xsigo(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Vacuum not identifying rows for removal..
Date: 2006-08-21 21:06:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
"Eamonn Kent" <ekent(at)xsigo(dot)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

In response to


pgsql-performance by date

Next:From: Jeff DavisDate: 2006-08-21 21:23:26
Subject: Re: How to get higher tps
Previous:From: Marty JiaDate: 2006-08-21 20:45:11
Subject: How to get higher tps

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