postgres.git / summary / log / commit / refs

commit    409d9390e8e944eab2ea4b98984cc5781d70e7d1
Author:   David Rowley <drowley@postgresql.org>
Date:     Sun Jul 04 10:29:57 2021 +0000
First released in: 15.0, 9.6.23, 10.18, 11.13, 12.8, 13.4, 14.0

    Doc: mention that VACUUM can't utilize over 1GB of RAM
    
    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 ba2f1eabcf0..2661bfde4b8 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1769,6 +1769,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>
 


[parent: 650e6359018a]