Update vacuum to mention analyze

diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index 6511563523c286587aa138fb641a55243402e59a..f77e1fb6730d906d012e5734123485d81172b4a1 100644 (file)
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -1,5 +1,5 @@
 
 
@@ -51,8 +51,6 @@ VACUUM [ VERBOSE ] ANALYZE [ table
        
    Updates column statistics used by the optimizer to
    determine the most efficient way to execute a query.
-   The statistics represent the disbursion of the data in each column.
-   This information is valuable when several execution paths are possible.
        
       
      
@@ -158,6 +156,13 @@ NOTICE:  Index index: Pages 28;
    tuples and number of pages stored in all classes.
   
 
+
+  
+   VACUUM ANALYZE collects statistics representing the
+   disbursion of the data in each column.
+   This information is valuable when several query execution paths are possible.
+  
+
   
    Running VACUUM
    periodically will increase the speed of the database in processing user queries.
@@ -179,11 +184,12 @@ NOTICE:  Index index: Pages 28;
     query may be executed at any time, however.  In particular, after
     copying a large class into Postgres 
     or after deleting a large number of
-    records, it may be a good idea to issue a VACUUM
+    records, it may be a good idea to issue a VACUUM ANALYZE
     query.  This will update the system catalogs with the results of all
     recent changes, and allow the Postgres 
     query optimizer to make better choices in planning user queries.
    
+