aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2021-07-04 22:29:16 +1200
committerDavid Rowley <drowley@postgresql.org>2021-07-04 22:29:16 +1200
commitb88e5fe60eef5decd3ccfd73566559dc6136cb61 (patch)
tree7d3d38a44138323dde2c64102db0a598fafb485c
parente033e260b9d0fcba969e5314be967429ade1b9ec (diff)
downloadpostgresql-b88e5fe60eef5decd3ccfd73566559dc6136cb61.tar.gz
postgresql-b88e5fe60eef5decd3ccfd73566559dc6136cb61.zip
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
-rw-r--r--doc/src/sgml/config.sgml6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 3eee9883595..1bbc631afe5 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1893,6 +1893,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>