database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-25 21:42:33 +03:00
Code

Doc: Fix misleading statement about VACUUM memory limits

Browse Source 
In ec34040af 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 ec34040af 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 ec34040af
This commit is contained in:
David Rowley 2021-08-09 16:45:35 +12:00
parent 4a3d806f38
commit deb6ffd4fd
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/src/sgml/config.sgml
View File

@ -1894,10 +1894,9 @@ include_dir 'conf.d'
setting <xref linkend="guc-autovacuum-work-mem"/>. setting <xref linkend="guc-autovacuum-work-mem"/>.
</para> </para>
<para> <para>
Additionally, <command>VACUUM</command> is only able to utilize up to Note that for the collection of dead tuple identifiers,
a maximum of <literal>1GB</literal> of memory, so <command>VACUUM</command> is only able to utilize up to a maximum of
<varname>maintenance_work_mem</varname> values higher than this have <literal>1GB</literal> of memory.
no effect on <command>VACUUM</command>.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -1921,6 +1920,13 @@ include_dir 'conf.d'
<filename>postgresql.conf</filename> file or on the server command <filename>postgresql.conf</filename> file or on the server command
line. line.
</para> </para>
<para>
For the collection of dead tuple identifiers, autovacuum is only able
to utilize up to a maximum of <literal>1GB</literal> of memory, so
setting <varname>autovacuum_work_mem</varname> to a value higher than
that has no effect on the number of dead tuples that autovacuum can
collect while scanning a table.
</para>
</listitem> </listitem>
</varlistentry> </varlistentry>