From 8c14912cc1d907fc10c94c3c52b98cde21c715a5 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 31 Jan 2007 04:13:28 +0000 Subject: [PATCH] Document need for periodic REINDEX in VACUUM FULL cases. --- doc/src/sgml/maintenance.sgml | 6 ++---- doc/src/sgml/ref/vacuum.sgml | 5 ++++- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 4b321ca31bf..764d378bb68 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -1,4 +1,4 @@ - + Routine Database Maintenance Tasks @@ -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. diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml index cf039113f64..86bdeb9291c 100644 --- a/doc/src/sgml/ref/vacuum.sgml +++ b/doc/src/sgml/ref/vacuum.sgml @@ -1,5 +1,5 @@ @@ -167,6 +167,9 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] ANALYZE [ most of the rows in a table and would like the table to physically shrink to occupy less disk space. VACUUM FULL will usually shrink the table more than a plain VACUUM would. + The option does not shrink indexes; a periodic + REINDEX is still recommended. In fact, it is often faster + to drop all indexes, VACUUM FULL, and recreate the indexes.