Skip to content

P
Postgres FD Implementation
Commit 8522e59e authored by Bruce Momjian's avatar Bruce Momjian
Browse files
Options

Add URL for: 

* Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY

>   http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php
parent a690d09a
Hide whitespace changes
Inline Side-by-side
Showing with 4 additions and 2 deletions
doc/TODO
View file @ 8522e59e
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) 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 The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. http://www.postgresql.org/docs/faqs.TODO.html.
...@@ -1142,6 +1142,7 @@ Indexes ...@@ -1142,6 +1142,7 @@ Indexes
to replace the existing index file. CREATE INDEX CONCURRENTLY does not to replace the existing index file. CREATE INDEX CONCURRENTLY does not
have this complication. This would allow index compaction without have this complication. This would allow index compaction without
downtime. downtime.
http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php
* Allow multiple indexes to be created concurrently, ideally via a * Allow multiple indexes to be created concurrently, ideally via a
single heap scan, and have pg_restore use it single heap scan, and have pg_restore use it
......
doc/src/FAQ/TODO.html
View file @ 8522e59e
...@@ -8,7 +8,7 @@ ...@@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <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/> <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>
<p>The most recent version of this document can be viewed at<br/> <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>. <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/> ...@@ -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 to replace the existing index file. CREATE INDEX CONCURRENTLY does not
have this complication. This would allow index compaction without have this complication. This would allow index compaction without
downtime. 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> </p>
</li><li>Allow multiple indexes to be created concurrently, ideally via a </li><li>Allow multiple indexes to be created concurrently, ideally via a
single heap scan, and have pg_restore use it single heap scan, and have pg_restore use it
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment