aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/TODO3
-rw-r--r--doc/src/FAQ/TODO.html3
2 files changed, 4 insertions, 2 deletions
diff --git a/doc/TODO b/doc/TODO
index 6c04e17a645..ea3c28285fe 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,7 +1,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Wed Mar 12 14:33:47 EDT 2008
+Last updated: Wed Mar 12 15:15:19 EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1142,6 +1142,7 @@ Indexes
to replace the existing index file. CREATE INDEX CONCURRENTLY does not
have this complication. This would allow index compaction without
downtime.
+ http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php
* Allow multiple indexes to be created concurrently, ideally via a
single heap scan, and have pg_restore use it
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 6f132c589b3..92a3bdf77fa 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -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: Wed Mar 12 14:33:47 EDT 2008
+Last updated: Wed Mar 12 15:15:19 EDT 2008
</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>.
@@ -998,6 +998,7 @@ first. There is also a developer's wiki at<br/>
to replace the existing index file. CREATE INDEX CONCURRENTLY does not
have this complication. This would allow index compaction without
downtime.
+ <a href="http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php">http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php</a>
</p>
</li><li>Allow multiple indexes to be created concurrently, ideally via a
single heap scan, and have pg_restore use it