postgres.git / summary / log / commit / refs

commit    56dcf00b04b87bd616dfe230323c758eb9c40722
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Sat Sep 25 06:12:15 2021 +0000

    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


 doc/src/sgml/monitoring.sgml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 4744f220647..ae9712e618f 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -2684,8 +2684,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
        <command>VACUUM</> 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>


[parent: d02eb8383edd]