Commit 17285959 authored by Bruce Momjian's avatar Bruce Momjian

Add URL for:

* Improve speed with indexes

  For large table adjustments during VACUUM FULL, it is faster to cluster
  or reindex rather than update the index.  Also, index updates can bloat
  the index.

>
>   http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php
parent 3a7d66b4
...@@ -2,7 +2,7 @@ ...@@ -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: Mon Apr 2 18:46:07 EDT 2007 Last updated: Mon Apr 2 18:48:47 EDT 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.
...@@ -1169,9 +1169,11 @@ Vacuum ...@@ -1169,9 +1169,11 @@ Vacuum
* Improve speed with indexes * Improve speed with indexes
For large table adjustments during VACUUM FULL, it is faster to For large table adjustments during VACUUM FULL, it is faster to cluster
reindex rather than update the index. Also, index updates can or reindex rather than update the index. Also, index updates can bloat
bloat the index. the index.
http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php
* Reduce lock time during VACUUM FULL by moving tuples with read lock, * Reduce lock time during VACUUM FULL by moving tuples with read lock,
then write lock and truncate table then write lock and truncate table
......
...@@ -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: Mon Apr 2 18:46:07 EDT 2007 Last updated: Mon Apr 2 18:48:47 EDT 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>.
...@@ -1037,9 +1037,11 @@ first. There is also a developer's wiki at<br/> ...@@ -1037,9 +1037,11 @@ first. There is also a developer's wiki at<br/>
<ul> <ul>
<li>Improve speed with indexes <li>Improve speed with indexes
<p> For large table adjustments during VACUUM FULL, it is faster to <p> For large table adjustments during VACUUM FULL, it is faster to cluster
reindex rather than update the index. Also, index updates can or reindex rather than update the index. Also, index updates can bloat
bloat the index. the index.
</p>
<p> <a href="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php">http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php</a>
</p> </p>
</li><li>Reduce lock time during VACUUM FULL by moving tuples with read lock, </li><li>Reduce lock time during VACUUM FULL by moving tuples with read lock,
then write lock and truncate table then write lock and truncate table
......
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