git.postgresql.org Git - postgresql.git/commitdiff

git projects / postgresql.git / commitdiff
? search:
summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 50371df)
docs: clarify new aggressive vacuum mode for multi-xacts
Fri, 2 Jul 2021 22:00:30 +0000 (18:00 -0400)
Fri, 2 Jul 2021 22:00:30 +0000 (18:00 -0400)
Reported-by: eric.mutta@gmail.com
Discussion: https://postgr.es/m/162395467510.686.11947486273299446208@wrigleys.postgresql.org

Backpatch-through: 14


diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 4b535809b63ed54a4408a512fbcbc01e210144c9..998a48fc25798e7bab1e4d2afd1d71e9bb27731d 100644 (file)
--- 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.
</para>
<para>
- As a safety device, an aggressive vacuum scan will occur for any table
- whose multixact-age is greater than
- <xref linkend="guc-autovacuum-multixact-freeze-max-age"/>. 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 <xref
+ linkend="vacuum-for-multixact-wraparound"/>) is greater than <xref
+ linkend="guc-autovacuum-multixact-freeze-max-age"/>. 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.
</para>
</sect3>
</sect2>
This is the main PostgreSQL git repository.
RSS Atom

AltStyle によって変換されたページ (->オリジナル) /