From 4e00382b9a9265a49ce7b5222cb00d852187f76b Mon Sep 17 00:00:00 2001
From: Magnus Hagander <magnus@hagander.net>
Date: Mon, 8 Dec 2008 15:11:42 +0000
Subject: [PATCH] Add note that autovacuum can use up several times
 maintenance_work_mem, with warning against setting it too high.

---
 doc/src/sgml/config.sgml | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 253cf8ee03..50cb5edb08 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.164.2.5 2008/07/18 17:33:40 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.164.2.6 2008/12/08 15:11:42 mha Exp $ -->
 
 <chapter Id="runtime-config">
   <title>Server Configuration</title>
@@ -860,6 +860,11 @@ SET ENABLE_SEQSCAN TO OFF;
         than <varname>work_mem</varname>.  Larger settings might improve
         performance for vacuuming and for restoring database dumps.
        </para>
+       <para>
+        Note that when autovacuum runs, up to
+        <xref linkend="guc-autovacuum-max-workers"> times this memory may be
+        allocated, so be careful not to set the default value too high.
+       </para>
       </listitem>
      </varlistentry>
 
-- 
2.50.0