Greg Stark <gsstark@mit.edu> writes:
> The plan Gavin Sherry and I were discussing at the Code Sprint was to store a
> single "most common xmin" xmin in the per-page special area. Then have a bit
> on each tuple indicating that the xmin isn't present in the tuple and instead
> to use the xmin from the page footer. Any tuples with other values of xmin
> would have to store that xmin normally.
This seems pretty unworkable --- anything that involves more than one
field layout for tuple headers is going to be a huge PITA.
regards, tom lane
