diff options
| -rw-r--r-- | doc/src/sgml/config.sgml | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 32c8fb8ea92..e500b1fdecc 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1618,10 +1618,9 @@ include_dir 'conf.d' 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>. + Note that for the collection of dead tuple identifiers, + <command>VACUUM</command> is only able to utilize up to a maximum of + <literal>1GB</literal> of memory. </para> </listitem> </varlistentry> @@ -1643,6 +1642,13 @@ include_dir 'conf.d' <filename>postgresql.conf</filename> file or on the server command line. </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> </varlistentry> |