"Michael Richards" <[EMAIL PROTECTED]> 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

Reply via email to