@ -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: Sun Jun 18 15:32:30 EDT 2006
Last updated: Sat Jun 24 19:44:48 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 > .
@ -1019,6 +1019,12 @@ first.
in maintaining clustering?
< / li > < li > Consider shrinking expired tuples to just their headers
< p > < a href = "http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php" > http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php< / a >
< / p >
< / li > < li > Allow heap reuse of UPDATEd rows if old and new versions are on the
same heap page?
< p > This is possible for same-page updates because a single index row
can point to both old and new values.
< a href = "http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php" > http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php< / a >
< / p >
< / li > < li > Auto-vacuum
< ul >