Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit deb6ffd

Browse files
committed
Doc: Fix misleading statement about VACUUM memory limits
In ec34040 I added a mention that there was no point in setting maintenance_work_limit to anything higher than 1GB for vacuum, but that was incorrect as ginInsertCleanup() also looks at what maintenance_work_mem is set to during VACUUM and that's not limited to 1GB. Here I attempt to make it more clear that the limitation is only around the number of dead tuple identifiers that we can collect during VACUUM. I've also added a note to autovacuum_work_mem to mention this limitation. I didn't do that in ec34040 as I'd had some wrong-headed ideas about just limiting the maximum value for that GUC to 1GB. Author: David Rowley Discussion: https://postgr.es/m/CAApHDvpGwOAvunp-E-bN_rbAs3hmxMoasm5pzkYDbf36h73s7w@mail.gmail.com Backpatch-through: 9.6, same as ec34040
1 parent 4a3d806 commit deb6ffd

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

doc/src/sgml/config.sgml

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1894,10 +1894,9 @@ include_dir 'conf.d'
18941894
setting <xref linkend="guc-autovacuum-work-mem"/>.
18951895
</para>
18961896
<para>
1897-
Additionally, <command>VACUUM</command> is only able to utilize up to
1898-
a maximum of <literal>1GB</literal> of memory, so
1899-
<varname>maintenance_work_mem</varname> values higher than this have
1900-
no effect on <command>VACUUM</command>.
1897+
Note that for the collection of dead tuple identifiers,
1898+
<command>VACUUM</command> is only able to utilize up to a maximum of
1899+
<literal>1GB</literal> of memory.
19011900
</para>
19021901
</listitem>
19031902
</varlistentry>
@@ -1921,6 +1920,13 @@ include_dir 'conf.d'
19211920
<filename>postgresql.conf</filename> file or on the server command
19221921
line.
19231922
</para>
1923+
<para>
1924+
For the collection of dead tuple identifiers, autovacuum is only able
1925+
to utilize up to a maximum of <literal>1GB</literal> of memory, so
1926+
setting <varname>autovacuum_work_mem</varname> to a value higher than
1927+
that has no effect on the number of dead tuples that autovacuum can
1928+
collect while scanning a table.
1929+
</para>
19241930
</listitem>
19251931
</varlistentry>
19261932

0 commit comments

Comments
 (0)