Skip to content

Commit 4a9960e

Browse files
committed
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
1 parent 437d74f commit 4a9960e

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

doc/src/sgml/config.sgml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1732,6 +1732,12 @@ include_dir 'conf.d'
17321732
too high. It may be useful to control for this by separately
17331733
setting <xref linkend="guc-autovacuum-work-mem"/>.
17341734
</para>
1735+
<para>
1736+
Additionally, <command>VACUUM</command> is only able to utilize up to
1737+
a maximum of <literal>1GB</literal> of memory, so
1738+
<varname>maintenance_work_mem</varname> values higher than this have
1739+
no effect on <command>VACUUM</command>.
1740+
</para>
17351741
</listitem>
17361742
</varlistentry>
17371743

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy