Document need for periodic REINDEX in VACUUM FULL cases.

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 80db11754b1d7bb5f725dde0be157d7c6b4d0431..a2d0f55e02744824480b3cdf0cf8049d15275f5d 100644 (file)
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -613,9 +613,7 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu
    for inefficient use of space: if all but a few index keys on a page have
    been deleted, the page remains allocated.  So a usage pattern in which all
    but a few keys in each range are eventually deleted will see poor use of
-   space.  The potential for bloat is not indefinite — at worst there
-   will be one key per page — but it may still be worthwhile to schedule
-   periodic reindexing for indexes that have such usage patterns.
+   space.  For such usage patterns, periodic reindexing is recommended.
   </para>
 
   <para>

diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index ef543f137255669d39fcb9a9a9afd6feaaace3d7..b50fc7579609282806bed4f53a198cca7bf53dc3 100644 (file)
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -167,6 +167,9 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">
     most of the rows in a table and would like the table to physically shrink
     to occupy less disk space.  <command>VACUUM FULL</command> will usually
     shrink the table more than a plain <command>VACUUM</command> would.
+    The <option>FULL</option> option does not shrink indexes; a periodic
+    <command>REINDEX</> is still recommended.  In fact, it is often faster
+    to drop all indexes, <command>VACUUM FULL</>, and recreate the indexes.
    </para>
 
    <para>