Re: More Tuple Madness

Oops, I guess I assumed that the alignment part was directly related to the
number of bytes until the next attribute rather than the actual alignment.

Is there any need for documentation on how this whole storage thing works?
I'd be more than willing to write it up.

-Michael

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Michael Richards" <miker(at)interchange(dot)ca>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Sent: Sunday, December 17, 2000 1:14 PM
Subject: Re: [HACKERS] More Tuple Madness

> "Michael Richards" <miker(at)interchange(dot)ca> writes:
> > The alignment seems to be wrong for type CHAR(1):
>
> No, the alignment is fine. A field's align constraint says where it has
> to start, not where the next field has to start. gender starts on a
> 4-byte boundary and is 5 bytes long, then we have one byte wasted for
> alignment of yearofbirth, then yearofbirth starts on a 2-byte boundary.
> Everyone's happy.
>
> regards, tom lane