database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-05 07:41:25 +03:00
Code Activity

Add:

Browse Source 
>
> * 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.
This commit is contained in:
Bruce Momjian
2007-01-31 03:17:49 +00:00
parent 62b2786b82
commit 99507b9a92
2 changed files with 15 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
doc/TODO
View File

@@ -2,7 +2,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
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 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.
@@ -909,6 +909,13 @@ Indexes
This is difficult because it requires datatype-specific knowledge. 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 * Inheritance

8
doc/src/FAQ/TODO.html
View File

@@ -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: Tue Jan 30 22:07:21 EST 2007 Last updated: Tue Jan 30 22:17:43 EST 2007
</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>.
@@ -820,6 +820,12 @@ first. There is also a developer's wiki at<br/>
</li><li>Consider compressing indexes by storing key values duplicated in </li><li>Consider compressing indexes by storing key values duplicated in
several rows as a single index entry several rows as a single index entry
<p> This is difficult because it requires datatype-specific knowledge. <p> This is difficult because it requires datatype-specific knowledge.
</p>
</li><li>Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
<p> 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.
</p> </p>
</li><li>Inheritance </li><li>Inheritance
<ul> <ul>