Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> 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?
Hmm ... I wonder if that has something to do with the performance
complaints we sometimes get about TOAST. VACUUM would presumably set
the bit, but in a never-vacuumed toast table this could be a problem.
regards, tom lane