diff options
| author | Michael Paquier <michael@paquier.xyz> | 2021-09-25 15:12:00 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2021-09-25 15:12:00 +0900 |
| commit | 52f8575a9e75e67ed7a7ae1585be28a85e85ae0e (patch) | |
| tree | dfc4a552e7f4a5b3d56602ed24d1e4d1037a7df9 | |
| parent | ca925fe3c4d3727679f00deedde83765b89c32bb (diff) | |
| download | postgresql-52f8575a9e75e67ed7a7ae1585be28a85e85ae0e.tar.gz postgresql-52f8575a9e75e67ed7a7ae1585be28a85e85ae0e.zip | |
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 5213bd3358b..6abb29ecafe 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -5679,8 +5679,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> |