|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.36 2004/12/02 19:28:48 tgl Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.37 2005/07/30 15:45:49 momjian Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -174,6 +174,15 @@ VACUUM [ FULL | FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">ta |
174 | 174 | to occupy less disk space. <command>VACUUM FULL</command> will usually |
175 | 175 | shrink the table more than a plain <command>VACUUM</command> would. |
176 | 176 | </para> |
| 177 | + |
| 178 | + <para> |
| 179 | + During <command>VACUUM</command> execution, there can be a substantial |
| 180 | + increase in I/O traffic, which cause poor performance for other active |
| 181 | + sessions. Therefore, it is sometimes advisable to use |
| 182 | + the cost-based vacuum delay feature. See <xref |
| 183 | + linkend="runtime" endterm="runtime-config-resource-vacuum-cost"> for more |
| 184 | + details. |
| 185 | + </para> |
177 | 186 | </refsect1> |
178 | 187 |
|
179 | 188 | <refsect1> |
@@ -229,6 +238,7 @@ VACUUM |
229 | 238 |
|
230 | 239 | <simplelist type="inline"> |
231 | 240 | <member><xref linkend="app-vacuumdb" endterm="app-vacuumdb-title"></member> |
| 241 | + <member><xref linkend="runtime" endterm="runtime-config-resource-vacuum-cost"></member> |
232 | 242 | </simplelist> |
233 | 243 | </refsect1> |
234 | 244 | </refentry> |
|