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

Re: BUG #4059: Vacuum full not always cleaning empty tables

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Mark Steben <msteben(at)autorevenue(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4059: Vacuum full not always cleaning empty tables
Date: 2008-03-26 01:24:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Mark Steben wrote:

> I sent an email to 'pgsql-bugs(at)postgresql(dot)org' entitled
>  'Possible bug with VACUUM FULL' and also an addendum
> But neglected to also send this bug report form.
> You can refer to those emails; in a nutshell, I have found that VACUUM FULL
> will not clean dead tuples out of an empty table when other queries are
> accessing the database. Test plans/scenarios are included.

Yes, if other sessions have open transactions whose start time predate
the start time of the transaction that deletes of tuples, those tuples
cannot be removed by VACUUM.  This is known and expected.  Is this
what's happening here?

Alvaro Herrera                      
The PostgreSQL Company - Command Prompt, Inc.

In response to


pgsql-bugs by date

Next:From: Eugen.KonkovDate: 2008-03-26 08:14:49
Subject: Re: BUG: PG do not use index
Previous:From: Tom LaneDate: 2008-03-26 01:04:36
Subject: Re: BUG #4058: xml_table() segfaults on null

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