From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: nikolai.berkoff@pm.me
Subject: Missing mention of autovacuum_work_mem
Date: Thu, 11 Mar 2021 09:07:35 +0000
Message-ID: <161545365522.10134.12195402324485546870@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/13/progress-reporting.html
Description:
The "vacuuming indexes" documentation has:
"If a table has any indexes, this will happen at least once per vacuum,
after the heap has been completely scanned. It may happen multiple times per
vacuum if maintenance_work_mem is insufficient to store the number of dead
tuples found."
should be something like
"If a table has any indexes, this will happen at least once per vacuum,
after the heap has been completely scanned. It may happen multiple times per
vacuum if the maximum memory is insufficient to store the number of dead
tuples found. The maximum memory is set via the maintenance_work_mem unless
it is an autovacuum then autovacuum_work_mem will be used."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, nikolai.berkoff@pm.me
Subject: Re: Missing mention of autovacuum_work_mem
In-Reply-To: <161545365522.10134.12195402324485546870@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox