Re: BUG #4059: Vacuum full not always cleaning empty tables - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #4059: Vacuum full not always cleaning empty tables
Date
Msg-id 20080326012406.GA10907@alvh.no-ip.org
Whole thread Raw
In response to BUG #4059: Vacuum full not always cleaning empty tables  ("Mark Steben" <msteben@autorevenue.com>)
Responses Re: BUG #4059: Vacuum full not always cleaning empty tables
List pgsql-bugs
Mark Steben wrote:

> I sent an email to 'pgsql-bugs@postgresql.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                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4058: xml_table() segfaults on null
Next
From:
Date:
Subject: Re: BUG: PG do not use index