1
1
<!--
2
- $Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.7 1999/12/07 22:41:41 momjian Exp $
2
+ $Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.8 2000/04/05 21:51:11 momjian Exp $
3
3
Postgres documentation
4
4
-->
5
5
@@ -51,8 +51,6 @@ VACUUM [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">table</replaceable>
51
51
<para>
52
52
Updates column statistics used by the optimizer to
53
53
determine the most efficient way to execute a query.
54
- The statistics represent the disbursion of the data in each column.
55
- This information is valuable when several execution paths are possible.
56
54
</para>
57
55
</listitem>
58
56
</varlistentry>
@@ -158,6 +156,13 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
158
156
tuples and number of pages stored in all classes.
159
157
</para>
160
158
159
+
160
+ <para>
161
+ <command>VACUUM ANALYZE</command> collects statistics representing the
162
+ disbursion of the data in each column.
163
+ This information is valuable when several query execution paths are possible.
164
+ </para>
165
+
161
166
<para>
162
167
Running <command>VACUUM</command>
163
168
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;
179
184
query may be executed at any time, however. In particular, after
180
185
copying a large class into <productname>Postgres</productname>
181
186
or after deleting a large number of
182
- records, it may be a good idea to issue a <command>VACUUM</command>
187
+ records, it may be a good idea to issue a <command>VACUUM ANALYZE </command>
183
188
query. This will update the system catalogs with the results of all
184
189
recent changes, and allow the <productname>Postgres</productname>
185
190
query optimizer to make better choices in planning user queries.
186
191
</para>
192
+
187
193
</refsect2>
188
194
</refsect1>
189
195
0 commit comments