aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2022-04-02 09:49:06 -0700
committerPeter Geoghegan <pg@bowt.ie>2022-04-02 09:49:06 -0700
commit32558a8bc3c0035e7b738e47b00ff6b4bfc96da8 (patch)
treebd4e67621e70717de14721e4e4419eed64a21d07
parentd480ae069e6c13dcb719b8c6aaf7a5540196a1b3 (diff)
downloadpostgresql-32558a8bc3c0035e7b738e47b00ff6b4bfc96da8.tar.gz
postgresql-32558a8bc3c0035e7b738e47b00ff6b4bfc96da8.zip
Doc: Remove MultiXact wraparound section link.
Remove circular "25.1.5.1. Multixacts And Wraparound" link that references the section that the link itself appears in. An explanation of MultiXactId age appears only a few sentences before the link, so there's no question that the link is superfluous at best. Oversight in commit d5409295. Author: Peter Geoghegan <pg@bowt.ie> Backpatch: 14-
-rw-r--r--doc/src/sgml/maintenance.sgml3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 34d72dba784..693c92d9cba 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -720,8 +720,7 @@ HINT: Stop the postmaster and vacuum that database in single-user mode.
<para>
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
+ occur for any table whose multixact-age 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