|
8 | 8 | <bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF"> |
9 | 9 | <h1><aname="section_1">PostgreSQL TODO List</a></h1> |
10 | 10 | <p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> |
11 | | -Last updated:Wed Apr4 22:08:46 EDT 2007 |
| 11 | +Last updated:Fri Apr6 22:48:08 EDT 2007 |
12 | 12 | </p> |
13 | 13 | <p>The most recent version of this document can be viewed at<br/> |
14 | 14 | <ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. |
@@ -1273,14 +1273,7 @@ <h1><a name="section_20">Miscellaneous Performance</a></h1> |
1273 | 1273 | </li><li>-<em>Merge xmin/xmax/cmin/cmax back into three header fields</em> |
1274 | 1274 | </li><li>Consider ways of storing rows more compactly on disk |
1275 | 1275 | <ul> |
1276 | | -<li>Support a smaller header for short variable-length fields? |
1277 | | -<p> One idea is to create zero-or-one-byte-header versions |
1278 | | - of varlena data types. In involves setting the high-bit and |
1279 | | - 0-127 length in the single-byte header, or clear the high bit |
1280 | | - and store the 7-bit ASCII value in the rest of the byte. |
1281 | | - The small-header versions have no alignment requirements. |
1282 | | -<ahref="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php</a> |
1283 | | -</p> |
| 1276 | +<li>-<em>Support a smaller header for short variable-length fields</em> |
1284 | 1277 | </li><li>Reduce the row header size? |
1285 | 1278 | </li><li>Consider reducing on-disk varlena length from four to two |
1286 | 1279 | because a heap row cannot be more than 64k in length |
|