| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Arrange to squeeze out the MINIMAL_TUPLE_PADDING in the tuple |
| Date: | 2008-10-28 15:51:03 |
| Message-ID: | 20081028155103.4A02E7545A4@cvs.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Arrange to squeeze out the MINIMAL_TUPLE_PADDING in the tuple representation
written to temp files by tuplesort.c and tuplestore.c. This saves 2 bytes per
row for 32-bit machines, and 6 bytes per row for 64-bit machines, which seems
worth the slight additional uglification of the tuple read/write routines.
Modified Files:
--------------
pgsql/src/backend/utils/sort:
tuplesort.c (r1.87 -> r1.88)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/sort/tuplesort.c?r1=1.87&r2=1.88)
tuplestore.c (r1.42 -> r1.43)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/sort/tuplestore.c?r1=1.42&r2=1.43)
pgsql/src/include/access:
htup.h (r1.101 -> r1.102)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/htup.h?r1=1.101&r2=1.102)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-10-28 17:13:52 | pgsql: Change WorkTableScan to not support backward scan. |
| Previous Message | Peter Eisentraut | 2008-10-28 14:09:45 | pgsql: Add WITH [NO] DATA clause to CREATE TABLE AS, per SQL. |