diff options
| author | Bruce Momjian <bruce@momjian.us> | 2000-04-05 21:51:11 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2000-04-05 21:51:11 +0000 |
| commit | 7c6bac0071c8ed0e47f63a88ed4f3a4e9a04edaa (patch) | |
| tree | f87c2d74fd9a573271c68e67ba568bace4a6a5ef | |
| parent | a7b1ff6619413398d7e69b0888b6672d6b9413a6 (diff) | |
| download | postgresql-7c6bac0071c8ed0e47f63a88ed4f3a4e9a04edaa.tar.gz postgresql-7c6bac0071c8ed0e47f63a88ed4f3a4e9a04edaa.zip | |
Update vacuum to mention analyze
| -rw-r--r-- | doc/src/sgml/ref/vacuum.sgml | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml index 6511563523c..f77e1fb6730 100644 --- a/doc/src/sgml/ref/vacuum.sgml +++ b/doc/src/sgml/ref/vacuum.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.7 1999/12/07 22:41:41 momjian Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.8 2000/04/05 21:51:11 momjian Exp $ Postgres documentation --> @@ -51,8 +51,6 @@ VACUUM [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">table</replaceable> <para> 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. </para> </listitem> </varlistentry> @@ -158,6 +156,13 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28; tuples and number of pages stored in all classes. </para> + + <para> + <command>VACUUM ANALYZE</command> collects statistics representing the + disbursion of the data in each column. + This information is valuable when several query execution paths are possible. + </para> + <para> Running <command>VACUUM</command> periodically will increase the speed of the database in processing user queries. @@ -179,11 +184,12 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28; query may be executed at any time, however. In particular, after copying a large class into <productname>Postgres</productname> or after deleting a large number of - records, it may be a good idea to issue a <command>VACUUM</command> + records, it may be a good idea to issue a <command>VACUUM ANALYZE</command> query. This will update the system catalogs with the results of all recent changes, and allow the <productname>Postgres</productname> query optimizer to make better choices in planning user queries. </para> + </refsect2> </refsect1> |