>
>
> Thanks
>
> Ike
>
>
>
>
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 21, 2006 2:06 PM
> To: Eamonn Kent
> Cc: pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] Vacuum not identifyi
:[EMAIL PROTECTED]
Sent: Monday, August 21, 2006 2:06 PM
To: Eamonn Kent
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Vacuum not identifying rows for removal..
"Eamonn Kent" <[EMAIL PROTECTED]> writes:
I am using PostgreSQL 8.1.4 for an embedded application.
: Monday, August 21, 2006 2:06 PM
To: Eamonn Kent
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Vacuum not identifying rows for removal..
"Eamonn Kent" <[EMAIL PROTECTED]> writes:
> I am using PostgreSQL 8.1.4 for an embedded application. For some
> reason, vacuum i
"Eamonn Kent" <[EMAIL PROTECTED]> 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 q
On Mon, 2006-08-21 at 11:50 -0700, Eamonn Kent wrote:
> So, my best guess is that something in our application is preventing
> vacuum from removing dead rows. What could cause this? Would it be
> caused by a long-living transaction? What is the best way to track
> the problem down...right now,