Re: tuptoaster.c must *not* use SnapshotAny - Mailing list pgsql-hackers

From Tom Lane
Subject Re: tuptoaster.c must *not* use SnapshotAny
Date
Msg-id 23199.1011276483@sss.pgh.pa.us
Whole thread Raw
In response to Re: tuptoaster.c must *not* use SnapshotAny  ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>)
List pgsql-hackers
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at> writes:
> I am concerned about the case where VACUUM FULL:
> 1. inserts heap tuple to new location using FrozenXid
> 2. updates original heap tuples's xmax

It doesn't matter whether it's FrozenXid or not.  The tuple is not
visible if it's got the wrong setting of HEAP_MOVED_OFF/IN.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Daniel Kalchev
Date:
Subject: Re: RC1 date?
Next
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: tuptoaster.c must *not* use SnapshotAny