Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Doc: mention that VACUUM can't utilize over 1GB of RAM
authorDavid Rowley <drowley@postgresql.org>
Sun, 4 Jul 2021 10:29:57 +0000 (22:29 +1200)
committerDavid Rowley <drowley@postgresql.org>
Sun, 4 Jul 2021 10:29:57 +0000 (22:29 +1200)
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

index ba2f1eabcf0e405a4ba6394fce62fb0e01713482..2661bfde4b8890d3a12c9d1bdb8c919328d9ee70 100644 (file)
@@ -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>