From 32558a8bc3c0035e7b738e47b00ff6b4bfc96da8 Mon Sep 17 00:00:00 2001
From: Peter Geoghegan <pg@bowt.ie>
Date: Sat, 2 Apr 2022 09:49:06 -0700
Subject: [PATCH] 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-
---
 doc/src/sgml/maintenance.sgml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 34d72dba78..693c92d9cb 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