diff options
| -rw-r--r-- | doc/TODO | 23 | ||||
| -rw-r--r-- | doc/src/FAQ/TODO.html | 23 |
2 files changed, 15 insertions, 31 deletions
@@ -2,7 +2,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Thu Sep 14 17:43:58 EDT 2006 +Last updated: Sat Sep 16 18:06:27 EDT 2006 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. @@ -1353,23 +1353,14 @@ Miscellaneous Performance * Consider ways of storing rows more compactly on disk - o Reorder physical storage order to reduce padding? - - This involves having the user-specified order of columns - be different from the physical order. SELECT * would - need to reorder the physical values to match the - user-specified ordering. - - o Store disk pages with no alignment/padding? - - This necessitates adding CPU-required padding when moving - rows from disk to memory. - o Support a smaller header for short variable-length fields? - One idea is to store the header in network byte order (high bits - first), and read the high bits to determine the header length. - http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php + 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 Reduce the row header size? diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index bd242da50d5..ed40f3d6de9 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@ <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <h1><a name="section_1">PostgreSQL TODO List</a></h1> <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> -Last updated: Thu Sep 14 17:43:58 EDT 2006 +Last updated: Sat Sep 16 18:06:27 EDT 2006 </p> <p>The most recent version of this document can be viewed at<br/> <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. @@ -1219,20 +1219,13 @@ first. </p> </li><li>Consider ways of storing rows more compactly on disk <ul> - <li>Reorder physical storage order to reduce padding? -<p> This involves having the user-specified order of columns - be different from the physical order. SELECT * would - need to reorder the physical values to match the - user-specified ordering. -</p> - </li><li>Store disk pages with no alignment/padding? -<p> This necessitates adding CPU-required padding when moving - rows from disk to memory. -</p> - </li><li>Support a smaller header for short variable-length fields? -<p> One idea is to store the header in network byte order (high bits - first), and read the high bits to determine the header length. - <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php</a> + <li>Support a smaller header for short variable-length fields? +<p> 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. + <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php</a> </p> </li><li>Reduce the row header size? </li></ul> |