diff options
| author | Michael Paquier | 2021-09-25 06:12:07 +0000 |
|---|---|---|
| committer | Michael Paquier | 2021-09-25 06:12:07 +0000 |
| commit | 26928441cbb4995fa1474c861d26d3318c8923f3 (patch) | |
| tree | 8a974e2790fe24b49ddbbd0b99709a6954ed3099 | |
| parent | 63b5b4a9a1a8e5a5a16c043bf1503e321debe1df (diff) | |
doc: Improve description of index vacuuming with GUCs
Index vacuums may happen multiple times depending on the number of dead
tuples stored, as of maintenance_work_mem for a manual VACUUM. For
autovacuum, this is controlled by autovacuum_work_mem instead, if set.
The documentation mentioned the former, but not the latter in the
context of autovacuum.
Reported-by: Nikolai Berkoff
Author: Laurenz Albe, Euler Taveira
Discussion: https://postgr.es/m/161545365522.10134.12195402324485546870@wrigleys.postgresql.org
Backpatch-through: 9.6
| -rw-r--r-- | doc/src/sgml/monitoring.sgml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 32932475340..16c927fcef3 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -3512,8 +3512,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid, <command>VACUUM</command> is currently vacuuming the indexes. 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 <xref linkend="guc-maintenance-work-mem"/> is insufficient to - store the number of dead tuples found. + if <xref linkend="guc-maintenance-work-mem"/> (or, in the case of autovacuum, + <xref linkend="guc-autovacuum-work-mem"/> if set) is insufficient to store + the number of dead tuples found. </entry> </row> <row> |