On Wed, Sep 21, 2011 at 1:03 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
> Hi,
>
> I notice that HeapTupleSatisfiesToast is not setting the
> HEAP_XMIN_COMMITTED bit, though it is reading it. Is there a reason for
> this? It seems to me that it'd make sense to have it set ... unless
> it's set by some other routine, somehow?
I think it's implied from the untoasted row. Notice that it's not
checking visibility either except in binary upgrade cases.
merlin
