Zdenek Kotala <[EMAIL PROTECTED]> writes:
> If I understand correctly then for read path (select) tuple is always
> HeapTuple, because we need support select xmax ... And DatumTuple is
> used for write path (insert/update) and it is "converted" to HeapTuple
> in heap_insert/heap_update function.
Tom Lane napsal(a):
Zdenek Kotala <[EMAIL PROTECTED]> writes:
I try to understand why HeapTupleHeaderData structure has t_datum
member. This is use only on few places and from my point of view this
information should be stored in the HeapTupleData structure or split
HeapTupleHeaderData it into
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> I try to understand why HeapTupleHeaderData structure has t_datum
> member. This is use only on few places and from my point of view this
> information should be stored in the HeapTupleData structure or split
> HeapTupleHeaderData it into two structure
I try to understand why HeapTupleHeaderData structure has t_datum
member. This is use only on few places and from my point of view this
information should be stored in the HeapTupleData structure or split
HeapTupleHeaderData it into two structures (DatumTupleHeaderData). The
idea behind my ques
