Re: heap vacuum & cleanup locks - Mailing list pgsql-hackers

From Tom Lane
Subject Re: heap vacuum & cleanup locks
Date
Msg-id 21371.1320877084@sss.pgh.pa.us
Whole thread Raw
In response to Re: heap vacuum & cleanup locks  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: heap vacuum & cleanup locks  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> As for what to do about all this, I think Tom's idea would work for
> good tuples, but the current freezing code can't handle dead tuples;
> it counts on those having been already removed.

I have not gone back to look at the code, but are you worried about the
fact that it doesn't consider replacing xmax with FrozenTransactionId?
Surely we could do that if we wanted.  It just never seemed necessary
before --- but if vacuum is to be allowed to punt repeatedly on the same
page, maybe we do need to cover the case.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cost estimates for parameterized paths
Next
From: Tom Lane
Date:
Subject: Re: heap vacuum & cleanup locks