diff options
| author | David Rowley <drowley@postgresql.org> | 2021-07-04 22:29:57 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2021-07-04 22:29:57 +1200 |
| commit | 409d9390e8e944eab2ea4b98984cc5781d70e7d1 (patch) | |
| tree | e6d6ebd64a5491aa8b8b13f94a3edba51dcb9288 /doc/src | |
| parent | 650e6359018a54287d99fcd9640fb24fa7209467 (diff) | |
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
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/config.sgml | 6 |
1 files changed, 6 insertions, 0 deletions
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> |