diff options
| author | David Rowley <drowley@postgresql.org> | 2021-07-04 22:32:46 +1200 |
|---|---|---|
| committer | David Rowley <drowley@postgresql.org> | 2021-07-04 22:32:46 +1200 |
| commit | 1c84f355ac58fca53752f6335309b48ce97d8d73 (patch) | |
| tree | 9cad1fc9b61196fe21cd0b93dd8fdc08a48c34a0 | |
| parent | 58f759fd030a2c2b067107140474eaf59c8f168a (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
| -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 41809f15bf2..ad33fe9c1bf 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1489,6 +1489,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> |