PostgreSQL TODO List
====================
-Last updated: Wed Apr 4 22:08:46 EDT 2007
+Last updated: Fri Apr 6 22:48:08 EDT 2007
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
* -Merge xmin/xmax/cmin/cmax back into three header fields
* Consider ways of storing rows more compactly on disk
- o Support a smaller header for short variable-length fields?
-
- One idea is to create zero-or-one-byte-header versions
- of varlena data types. In involves setting the high-bit and
- 0-127 length in the single-byte header, or clear the high bit
- and store the 7-bit ASCII value in the rest of the byte.
- The small-header versions have no alignment requirements.
- http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php
-
+ o -Support a smaller header for short variable-length fields
o Reduce the row header size?
o Consider reducing on-disk varlena length from four to two
because a heap row cannot be more than 64k in length
-Last updated: Wed Apr 4 22:08:46 EDT 2007
+Last updated: Fri Apr 6 22:48:08 EDT 2007
The most recent version of this document can be viewed at
-Merge xmin/xmax/cmin/cmax back into three header fields
Consider ways of storing rows more compactly on disk
-
Support a smaller header for short variable-length fields?
-
One idea is to create zero-or-one-byte-header versions
- of varlena data types. In involves setting the high-bit and
- 0-127 length in the single-byte header, or clear the high bit
- and store the 7-bit ASCII value in the rest of the byte.
- The small-header versions have no alignment requirements.
-
+
-Support a smaller header for short variable-length fields
Reduce the row header size?
Consider reducing on-disk varlena length from four to two
because a heap row cannot be more than 64k in length