Re: [HACKERS] Tuple alignment

Gregory Stark <[EMAIL PROTECTED]> writes: > "Tom Lane" <[EMAIL PROTECTED]> writes: >> The OID trick doesn't work very well either. > expn "OID trick"? See htup.h concerning where we stick OID into a tuple that has OID. regards, tom lane ---(end of

Re: [HACKERS] Tuple alignment

"Tom Lane" <[EMAIL PROTECTED]> writes: > Heikki Linnakangas <[EMAIL PROTECTED]> writes: >> Why do we require that t_hoff is MAXALIGNed? ISTM that if the first >> field in a tuple doesn't require alignment, it could be stored >> immediately after the null bitmap, without padding. > > Then the in

Re: [HACKERS] Tuple alignment

Heikki Linnakangas <[EMAIL PROTECTED]> writes: > Why do we require that t_hoff is MAXALIGNed? ISTM that if the first > field in a tuple doesn't require alignment, it could be stored > immediately after the null bitmap, without padding. Then the intra-tuple alignment would be unpredictable. The

[HACKERS] Tuple alignment

Why do we require that t_hoff is MAXALIGNed? ISTM that if the first field in a tuple doesn't require alignment, it could be stored immediately after the null bitmap, without padding. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com ---(end of broadca