Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > New versions of all these patches, plus one more patch which > removes the behavior that HeapTupleGetUpdateXid checks for > aborted updates. (Turns out this was necessary to get freezing > right.) My previous patch to avoid InvalidXid as page prune > point is reverted in there, too (no longer necessary.)
Does this mean that when HeapTupleSatisfiesVacuum() returns HEAPTUPLE_DELETE_IN_PROGRESS it is no longer possible for HeapTupleHeaderGetUpdateXid() to return InvalidTransactionId? -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
