Re: Questions about HeapTupleHeaderData - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Questions about HeapTupleHeaderData
Date
Msg-id 23238.1219328136@sss.pgh.pa.us
Whole thread Raw
In response to Re: Questions about HeapTupleHeaderData  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
List pgsql-hackers
Zdenek Kotala <Zdenek.Kotala@Sun.COM> 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.

No, DatumTuple is used for any free-standing composite-type Datum.
Thinking about it as "write path" and "read path" seems to me to
be missing the mark entirely.  In general most tuple-reading code
is supposed to work with either.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: About a message when "pg_ctl -w start" failed
Next
From: Peter Eisentraut
Date:
Subject: Re: A smaller default postgresql.conf