From: | tgl(at)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src backend/access/common/heaptuple.c ba ... |
Date: | 2002-05-27 19:53:33 |
Message-ID: | 20020527195333.9301A476058@postgresql.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql
Changes by: tgl(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-05-27 21:59:12 | pgsql/contrib/dblink README.dblink dblink.c db ... |
Previous Message | Bruce Momjian - CVS | 2002-05-25 22:44:14 | pgsql/doc TODO |