Add:

>
> * Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
>
>   This is difficult because you must upgrade to an exclusive table lock
>   to replace the existing index file.  CREATE INDEX CONCURRENTLY does not
>   have this complication.  This would allow index compaction without
>   downtime.

diff --git a/doc/TODO b/doc/TODO
index 483497e2c4d9c9743ae5ff541c64ed0810937895..fcae1e74dfc9ba620ca93873789e636a3edf49d0 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Tue Jan 30 22:07:21 EST 2007
+Last updated:      Tue Jan 30 22:17:43 EST 2007
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -909,6 +909,13 @@ Indexes
 
   This is difficult because it requires datatype-specific knowledge.
 
+* Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
+
+  This is difficult because you must upgrade to an exclusive table lock
+  to replace the existing index file.  CREATE INDEX CONCURRENTLY does not
+  have this complication.  This would allow index compaction without
+  downtime.
+
 
 * Inheritance
 

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 34bd53334a6763d79afd843a05ef2034432c8182..513b325d225b5ca5c9519e160443d9850583ead8 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 Jan 30 22:07:21 EST 2007
+Last updated:           Tue Jan 30 22:17:43 EST 2007
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -820,6 +820,12 @@ first.  There is also a developer's wiki at
   Consider compressing indexes by storing key values duplicated in
   several rows as a single index entry
   This is difficult because it requires datatype-specific knowledge.
+
+  Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
+  This is difficult because you must upgrade to an exclusive table lock
+  to replace the existing index file.  CREATE INDEX CONCURRENTLY does not
+  have this complication.  This would allow index compaction without
+  downtime.
 
   Inheritance