aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2007-01-31 03:07:36 +0000
committerBruce Momjian <bruce@momjian.us>2007-01-31 03:07:36 +0000
commit62b2786b82ac985c4c37eed9ebdd384ffa7bd5a0 (patch)
tree9be8d1d2aa73b080387fa66c7c04032d59d24062
parentaca00a8b988e07525a152970def9efed2970693d (diff)
downloadpostgresql-62b2786b82ac985c4c37eed9ebdd384ffa7bd5a0.tar.gz
postgresql-62b2786b82ac985c4c37eed9ebdd384ffa7bd5a0.zip
Update for VACUUM FULL:
< reindex rather than update the index. > reindex rather than update the index. Also, index updates can > bloat the index.
-rw-r--r--doc/TODO5
-rw-r--r--doc/src/FAQ/TODO.html5
2 files changed, 6 insertions, 4 deletions
diff --git a/doc/TODO b/doc/TODO
index cb7a65c89ca..483497e2c4d 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
PostgreSQL TODO List
====================
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Tue Jan 30 17:50:14 EST 2007
+Last updated: Tue Jan 30 22:07:21 EST 2007
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1033,7 +1033,8 @@ Vacuum
* Improve speed with indexes
For large table adjustments during VACUUM FULL, it is faster to
- reindex rather than update the index.
+ reindex rather than update the index. Also, index updates can
+ bloat the index.
* Reduce lock time during VACUUM FULL by moving tuples with read lock,
then write lock and truncate table
diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 2ba91ef778e..34bd53334a6 100644
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -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: Tue Jan 30 17:50:14 EST 2007
+Last updated: Tue Jan 30 22:07:21 EST 2007
</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>.
@@ -929,7 +929,8 @@ first. There is also a developer's wiki at<br/>
<ul>
<li>Improve speed with indexes
<p> For large table adjustments during VACUUM FULL, it is faster to
- reindex rather than update the index.
+ reindex rather than update the index. Also, index updates can
+ bloat the index.
</p>
</li><li>Reduce lock time during VACUUM FULL by moving tuples with read lock,
then write lock and truncate table