On Tuesday 31 July 2007 Tom Lane's cat, walking on the keyboard, wrote:
> > Moreover why it does not need transaction
> > visibility as an ordinary tuple (xmin, cmin, cmax, xmax)?
> Datums are values. '42'::int does not need visibility information;
> its value is always the same.
Maybe I understand something more, but I'm still in doubt about the tuple
header. In the htup.h file you find:
typedef struct HeapTupleHeaderData
maybe I cannot get the meaning of the above t_datum in the tuple header, can
anyone explain me that?
In response to
pgsql-novice by date
|Next:||From: Tom Lane||Date: 2007-08-06 15:19:23|
|Subject: Re: Atomic/locked "allocation" of table row? |
|Previous:||From: Sten Daniel Soersdal||Date: 2007-08-06 14:30:38|
|Subject: Re: Atomic/locked "allocation" of table row?|