Tom Lane 3212cf9417 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.		2002-05-27 19:53:33 +00:00
..
Makefile	Fix problem reported by Alex Korn: if a relation has been dropped and	2001-11-02 16:30:29 +00:00
heapam.c	Wups, managed to break ANALYZE with one aspect of that heap_fetch change.	2002-05-24 19:52:43 +00:00
hio.c	Commit to match discussed elog() changes. Only update is that LOG is	2002-03-02 21:39:36 +00:00
tuptoaster.c	Distinguish between MaxHeapAttributeNumber and MaxTupleAttributeNumber,	2002-05-27 19:53:33 +00:00