Thread: pgsql/src backend/access/common/heaptuple.c ba ...

pgsql/src backend/access/common/heaptuple.c ba ...

From
tgl@postgresql.org (Tom Lane)
Date:
CVSROOT:    /cvsroot
Module name:    pgsql
Changes by:    tgl@postgresql.org    02/05/27 15:53:33

Modified files:
    src/backend/access/common: heaptuple.c
    src/backend/access/heap: tuptoaster.c
    src/include/access: htup.h

Log message:
    Distinguish between MaxHeapAttributeNumber and MaxTupleAttributeNumber,
    where the latter is made slightly larger to allow for in-memory tuples
    containing resjunk attributes.  Responds to today's complaint that one
    cannot UPDATE a table containing the allegedly-legal maximum number of
    columns.

    Also, apply Manfred Koizar's recent patch to avoid extra alignment padding
    when there is a null bitmap.  This saves bytes in some cases while not
    creating any backward-compatibility problem AFAICS.