Add URL for:

* Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY

>   http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php
This commit is contained in:
Bruce Momjian 2008-03-12 19:15:25 +00:00
parent a690d09aab
commit 8522e59e13
2 changed files with 4 additions and 2 deletions

View File

@ -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

View File

@ -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