Re: Reduce per tuple overhead (bitmap)

Manfred Koizar <mkoi-pg@aon.at> writes:
> This small patch makes the length of the null bitmap a multiple
> of 1 byte (has been a multiple of 4 bytes previously), thus saving
> MAXIMUM_ALIGNOF (4 or 8 on modern platforms) bytes per on-disk-tuple
> in certain cases (depending on number of attributes and if there is
> at least one null attribute).
> Though it changes the on-disk-format, there's no need to initdb,
> because data offsets are stored in t_hoff for each tuple.  So this
> patch can be applied to HEAD and to the 7.2 branch.

I've applied this to CVS tip.  I do not think it is appropriate for
7.2 branch, however, since it's not a bug fix.

            regards, tom lane