Add UPDATE entry for row reuse.

>
> * Allow heap reuse of UPDATEd rows if old and new versions are on the
>   same heap page?
>
>   This is possible for same-page updates because a single index row
>   can point to both old and new values.
>   http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php

diff --git a/doc/TODO b/doc/TODO
index 7200d10736f5439674245abc0f796e3b3951c465..826ef81869dd7963b8311a32d07a7563b3e27afa 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Sun Jun 18 15:32:30 EDT 2006
+Last updated:      Sat Jun 24 19:44:48 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1131,6 +1131,13 @@ Vacuum
 
   http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php
 
+* Allow heap reuse of UPDATEd rows if old and new versions are on the
+  same heap page?
+
+  This is possible for same-page updates because a single index row
+  can point to both old and new values.
+  http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
+
 * Auto-vacuum
 
    o Use free-space map information to guide rfilling

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 1d7feb5b553b97c4c8fac76a7595dc60fac66046..78fb8077a731ddad9e6ec554703ce110831c5316 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-Last updated:           Sun Jun 18 15:32:30 EDT 2006
+Last updated:           Sat Jun 24 19:44:48 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1019,6 +1019,12 @@ first.
   in maintaining clustering?
   Consider shrinking expired tuples to just their headers
   http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php
+
+  Allow heap reuse of UPDATEd rows if old and new versions are on the
+  same heap page?
+  This is possible for same-page updates because a single index row
+  can point to both old and new values.
+  http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
 
   Auto-vacuum