Manfred Koizar <mkoi-pg@aon.at> writes:
> On Sat, 20 Jul 2002 16:27:14 -0400, Tom Lane <tgl@sss.pgh.pa.us>
> wrote:
>> I'd recommend redesigning the HeapTupleHeaderSet macros so that they
>> do not do any setting of t_infomask bits, or even take any conditional
>> action based on them,
> The HEAP_XMIN_IS_XMAX bit is exclusively managed by these macros.
> Pulling the handling of this bit out of the macros and spreading it to
> the places, where the macros are used, cannot make the whole thing
> more robust. This would mean, the caller had to decide whether to
> store Cmax into t_cid or t_xmax...
But the present scheme is very obviously not robust.
> Anyway, with this patch applied the heap tuple header changes should
> be able to survive the next two weeks. I don't want to hack together
> a quick change now, before I go on vacation. Let's find the perfect
> solution, when I'm back ...
I'm on the road too. But I want to see a different solution before
we release. I do not trust the current code at all.
regards, tom lane
