Update documentation to mention that autovacuum also does analyze so we

don't need to recommend nightly analyzes anymore unless autovacuum is off.

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 5eacf5fcfd362f0deb462179c9c9619599b76cbe..40eecdc376ef0c335dfd27eed897d31229d63f08 100644 (file)
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Routine Database Maintenance Tasks
@@ -262,12 +262,19 @@
    
 
    
-    Recommended practice for most sites is to schedule a database-wide
-    ANALYZE once a day at a low-usage time of day; this can
-    usefully be combined with a nightly VACUUM.  However,
-    sites with relatively slowly changing table statistics might find that
-    this is overkill, and that less-frequent ANALYZE runs
-    are sufficient.
+    Fortunately, autovacuum () monitors table
+    activity and performs ANALYZEs when necessary.  This
+    eliminates the need for administrators to manually schedule
+    ANALYZE.
+   
+
+   
+    For those not using autovacuum, one approach is to schedule a
+    database-wide ANALYZE once a day at a low-usage time of
+    day; this can usefully be combined with a nightly VACUUM.
+    However, sites with relatively slowly changing table statistics might
+    find that this is overkill, and that less-frequent ANALYZE
+    runs are sufficient.