Re: Remembering bug #6123

I wrote:
>> ... It ought to be comparing the tuple's xmax to
>> es_output_cid.

Sigh, need to go find some caffeine.  Obviously, it needs to check the
tuple's cmax, not xmax.  And that means the patch will be a bit more
invasive than this, because heap_update and heap_delete don't return
that information at present.

			regards, tom lane