From c552e171d16e461c7af60cfe1a891c87be9cbbbf Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 2 Jul 2021 18:00:30 -0400 Subject: [PATCH] docs: clarify new aggressive vacuum mode for multi-xacts Reported-by: eric.mutta@gmail.com Discussion: https://postgr.es/m/162395467510.686.11947486273299446208@wrigleys.postgresql.org Backpatch-through: 14 --- doc/src/sgml/maintenance.sgml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 4b535809b6..998a48fc25 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -697,14 +697,14 @@ HINT: Stop the postmaster and vacuum that database in single-user mode. - As a safety device, an aggressive vacuum scan will occur for any table - whose multixact-age is greater than - . Aggressive - vacuum scans will also occur progressively for all tables, starting with - those that have the oldest multixact-age, if the amount of used member - storage space exceeds the amount 50% of the addressable storage space. - Both of these kinds of aggressive scans will occur even if autovacuum is - nominally disabled. + As a safety device, an aggressive vacuum scan will + occur for any table whose multixact-age (see ) is greater than . Also, if the + storage occupied by multixacts members exceeds 2GB, aggressive vacuum + scans will occur more often for all tables, starting with those that + have the oldest multixact-age. Both of these kinds of aggressive + scans will occur even if autovacuum is nominally disabled.