From 301d9bb63edc24123f42aded5210617d6e597296 Mon Sep 17 00:00:00 2001
From: David Rowley <drowley@postgresql.org>
Date: Sun, 4 Jul 2021 22:32:06 +1200
Subject: [PATCH] Doc: mention that VACUUM can't utilize over 1GB of RAM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit
Document that setting maintenance_work_mem to values over 1GB has no
effect on VACUUM.
Reported-by: MartÃn Marqués
Author: Laurenz Albe
Discussion: https://postgr.es/m/CABeG9LsZ2ozUMcqtqWu_-GiFKB17ih3p8wBHXcpfnHqhCnsc7A%40mail.gmail.com
Backpatch-through: 9.6, oldest supported release
---
doc/src/sgml/config.sgml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index f70b605ac70..a98919ae90f 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1529,6 +1529,12 @@ include_dir 'conf.d'
too high. It may be useful to control for this by separately
setting <xref linkend="guc-autovacuum-work-mem">.
</para>
+ <para>
+ Additionally, <command>VACUUM</command> is only able to utilize up to
+ a maximum of <literal>1GB</literal> of memory, so
+ <varname>maintenance_work_mem</varname> values higher than this have
+ no effect on <command>VACUUM</command>.
+ </para>
</listitem>
</varlistentry>
--
2.39.5