Update for VACUUM FULL:

<   reindex rather than update the index.
>   reindex rather than update the index.  Also, index updates can
>   bloat the index.
This commit is contained in:
Bruce Momjian 2007-01-31 03:07:36 +00:00
parent aca00a8b98
commit 62b2786b82
2 changed files with 6 additions and 4 deletions

View File

@ -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

View File

@ -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