Skip to content
Snippets Groups Projects
Commit 7afc827c authored by Bruce Momjian's avatar Bruce Momjian
Browse files

Add URLs for: 

* Consider compressing indexes by storing key values duplicated in
  several rows as a single index entry
>
>   http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php
>   http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php
>
parent 512775e2
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
doc/TODO
+ 6
− 1
View file @ 7afc827c
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
Last updated: Thu Mar 6 17:04:50 EST 2008 Last updated: Thu Mar 6 17:09:38 EST 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.
...@@ -1028,6 +1028,11 @@ Indexes ...@@ -1028,6 +1028,11 @@ Indexes
* Consider compressing indexes by storing key values duplicated in * Consider compressing indexes by storing key values duplicated in
several rows as a single index entry several rows as a single index entry
http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php
* Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY * Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
This is difficult because you must upgrade to an exclusive table lock This is difficult because you must upgrade to an exclusive table lock
......
doc/src/FAQ/TODO.html
+ 5
− 1
View file @ 7afc827c
...@@ -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: Thu Mar 6 17:04:50 EST 2008 Last updated: Thu Mar 6 17:09:38 EST 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>.
...@@ -907,6 +907,10 @@ first. There is also a developer's wiki at<br/> ...@@ -907,6 +907,10 @@ first. There is also a developer's wiki at<br/>
</p> </p>
</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> <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00341.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php">http://archives.postgresql.org/pgsql-hackers/2007-02/msg01264.php</a>
<a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00465.php</a>
</p>
</li><li>Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY </li><li>Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
<p> This is difficult because you must upgrade to an exclusive table lock <p> This is difficult because you must upgrade to an exclusive table lock
to replace the existing index file. CREATE INDEX CONCURRENTLY does not to replace the existing index file. CREATE INDEX CONCURRENTLY does not
......
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