Duplicate:

< * Maintain a map of recently-expired rows
<
<   This allows vacuum to target specific pages for possible free space
<   without requiring a sequential scan.
<
Update entry:

>   One complexity is that index entries still have to be vacuumed, and
>   doing this without an index scan (by using the heap values to find the
>   index entry) might be slow and unreliable, especially for user-defined
>   index functions.

diff --git a/doc/TODO b/doc/TODO
index ab145472bdaa73440d3f5b26684db9402a844c64..7c88a4afe33216459eb3ff1267a93f30b5e8bee7 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Tue Aug 30 19:25:23 EDT 2005
+Last updated:      Thu Sep  1 20:49:44 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -810,11 +810,6 @@ Vacuum
   write lock. However, the read lock promotion to write lock could lead
   to deadlock situations.
 
-* Maintain a map of recently-expired rows
-
-  This allows vacuum to target specific pages for possible free space 
-  without requiring a sequential scan.
-
 * Auto-fill the free space map by scanning the buffer cache or by
   checking pages written by the background writer
 * Create a bitmap of pages that need vacuuming
@@ -823,6 +818,10 @@ Vacuum
   writer or some other process record pages that have expired rows, then
   VACUUM can look at just those pages rather than the entire table.  In
   the event of a system crash, the bitmap would probably be invalidated.
+  One complexity is that index entries still have to be vacuumed, and
+  doing this without an index scan (by using the heap values to find the
+  index entry) might be slow and unreliable, especially for user-defined
+  index functions.
 
 * %Add system view to show free space map contents
 

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 734597a96488aec6e0a6f7d2573306c1ea8bf77e..f24c9a5605f6f3899783cbcc6757c914c653c7cf 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:           Tue Aug 30 19:25:23 EDT 2005
+Last updated:           Thu Sep  1 20:49:44 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -730,10 +730,6 @@ first.
   Moved tuples are invisible to other backends so they don't require a
   write lock. However, the read lock promotion to write lock could lead
   to deadlock situations.
-
-  Maintain a map of recently-expired rows
-  This allows vacuum to target specific pages for possible free space 
-  without requiring a sequential scan.
 
   Auto-fill the free space map by scanning the buffer cache or by
   checking pages written by the background writer
@@ -742,6 +738,10 @@ first.
   writer or some other process record pages that have expired rows, then
   VACUUM can look at just those pages rather than the entire table.  In
   the event of a system crash, the bitmap would probably be invalidated.
+  One complexity is that index entries still have to be vacuumed, and
+  doing this without an index scan (by using the heap values to find the
+  index entry) might be slow and unreliable, especially for user-defined
+  index functions.
 
   %Add system view to show free space map contents
   Auto-vacuum