|
|
|
|
@ -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 |
|
|
|
|
|
Bruce Momjian
18 years ago