Re: No long-lived transaction, still can't delete tuples - Mailing list pgsql-general

Lincoln Yeoh <lyeoh@pop.jaring.my> writes:
> At 06:59 PM 4/24/02 -0400, Tom Lane wrote:
>> Until client A returns from his lunch break, you'll not be able to
>> vacuum the trash that client B generated, even though B has committed
>> his changes.

> Does just a BEGIN without anything else hold up vacuum? It doesn't seem to
> for 7.1.3. Whereas a BEGIN followed by a select from a table holds up
> vacuum once vacuum reaches the relevant table.

You're confusing obtaining a lock with determining xmin for tuple
removal purposes.

> BEGIN followed by select
> (1), causes vacuum to stop with:
> ERROR:  Parent tuple was not found

Oh?  If you have a repeatable example of that, I'd like to see it.

            regards, tom lane