|
1 | 1 | <!-- |
2 | | -$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.8 2000/04/05 21:51:11 momjian Exp $ |
| 2 | +$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.9 2000/04/14 17:37:54 momjian Exp $ |
3 | 3 | Postgres documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -179,15 +179,15 @@ NOTICE: Index <replaceable class="PARAMETER">index</replaceable>: Pages 28; |
179 | 179 | The open database is the target for <command>VACUUM</command>. |
180 | 180 | </para> |
181 | 181 | <para> |
182 | | - We recommend that active production databases be cleaned nightly, in order |
183 | | -to keep statistics relatively current. The<command>VACUUM</command> |
184 | | -query may be executed at any time, however. In particular, after |
185 | | -copying a large class into<productname>Postgres</productname> |
186 | | -or after deleting a large number of |
187 | | -records, it may be a good idea to issue a <command>VACUUM ANALYZE</command> |
188 | | -query. This will update the system catalogs withthe results of all |
189 | | -recent changes, and allow the<productname>Postgres</productname> |
190 | | -query optimizer to make betterchoices in planning user queries. |
| 182 | + We recommend that active production databases be |
| 183 | + <command>VACUUMM</command>-ed nightly, in order to keep remove |
| 184 | +expired rows. After copying a large class into |
| 185 | + <productname>Postgres</productname>or after deleting a large number |
| 186 | +of records, it may be a good idea to issue a <command>VACUUM |
| 187 | +ANALYZE</command> query. This will update the system catalogs with |
| 188 | +the results of all recent changes, and allowthe |
| 189 | + <productname>Postgres</productname>query optimizer to make better |
| 190 | + choices in planning user queries. |
191 | 191 | </para> |
192 | 192 |
|
193 | 193 | </refsect2> |
|