From 2ab9997ec2ad1def54f6e0fe846f1838581fe8d3 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sat, 30 Jul 2005 15:45:49 +0000
Subject: [PATCH] Patch to mention cost-based delay in vacuum reference

Alvaro Herrera
---
 doc/src/sgml/ref/vacuum.sgml | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index e020c9a9ac..1c90fe4ef1 100644
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.36 2004/12/02 19:28:48 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.37 2005/07/30 15:45:49 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -174,6 +174,15 @@ VACUUM [ FULL | FREEZE ] [ VERBOSE ] ANALYZE [ <replaceable class="PARAMETER">ta
     to occupy less disk space.  <command>VACUUM FULL</command> will usually
     shrink the table more than a plain <command>VACUUM</command> would.
    </para>
+
+   <para>
+    During <command>VACUUM</command> execution, there can be a substantial
+    increase in I/O traffic, which cause poor performance for other active
+    sessions.  Therefore, it is sometimes advisable to use
+    the cost-based vacuum delay feature.  See <xref
+    linkend="runtime" endterm="runtime-config-resource-vacuum-cost"> for more
+    details.
+   </para>
  </refsect1>
 
  <refsect1>
@@ -229,6 +238,7 @@ VACUUM
 
   <simplelist type="inline">
    <member><xref linkend="app-vacuumdb" endterm="app-vacuumdb-title"></member>
+   <member><xref linkend="runtime" endterm="runtime-config-resource-vacuum-cost"></member>
   </simplelist>
  </refsect1>
 </refentry>
-- 
2.40.0