postgres.git / summary / log / commit / refs

commit    e3a4e9edd5c0ed1d1ae1ec00fbc27cf8f8598515
Author:   Fujii Masao <fujii@postgresql.org>
Date:     Fri Jun 12 02:08:33 2026 +0000

    doc: fix reference for finding replication slots to drop
    
    Commit a70bce43fb added instructions on how to recover if PostgreSQL
    refuses to issue new transaction IDs because of imminent wraparound,
    but when describing how to find replication slots that should be dropped,
    it referred to pg_stat_replication where it should have referenced
    pg_replication_slots.
    
    In passing, decorate references to views with <structname> tags.
    
    Backpatch to all supported versions.
    
    Reported-By: Sanjaya Waruna <sanjaya.waruna@gmail.com>
    Author: Laurenz Albe <laurenz.albe@cybertec.at>
    Reviewed-by: Robert Treat <rob@xzilla.net>
    Reviewed-by: Fujii Masao <masao.fujii@gmail.com>
    Discussion: https://postgr.es/m/176767268098.1084085.10345048667224193115@wrigleys.postgresql.org
    Backpatch-through: 14


 doc/src/sgml/maintenance.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 3aae2a53a1f..1ab5bfd0ae4 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -663,20 +663,20 @@ HINT:  Stop the postmaster and vacuum that database in single-user mode.
     <orderedlist>
      <listitem>
       <simpara>Resolve old prepared transactions. You can find these by checking
-       <link linkend="view-pg-prepared-xacts">pg_prepared_xacts</link> for rows where
+       <link linkend="view-pg-prepared-xacts"><structname>pg_prepared_xacts</structname></link> for rows where
        <literal>age(transactionid)</literal> is large. Such transactions should be
        committed or rolled back.</simpara>
      </listitem>
      <listitem>
       <simpara>End long-running open transactions. You can find these by checking
-       <link linkend="monitoring-pg-stat-activity-view">pg_stat_activity</link> for rows where
+       <link linkend="monitoring-pg-stat-activity-view"><structname>pg_stat_activity</structname></link> for rows where
        <literal>age(backend_xid)</literal> or <literal>age(backend_xmin)</literal> is
        large. Such transactions should be committed or rolled back, or the session
        can be terminated using <literal>pg_terminate_backend</literal>.</simpara>
      </listitem>
      <listitem>
       <simpara>Drop any old replication slots. Use
-       <link linkend="monitoring-pg-stat-replication-view">pg_stat_replication</link> to
+       <link linkend="view-pg-replication-slots"><structname>pg_replication_slots</structname></link> to
        find slots where <literal>age(xmin)</literal> or <literal>age(catalog_xmin)</literal>
        is large. In many cases, such slots were created for replication to servers that no
        longer exist, or that have been down for a long time. If you drop a slot for a server


[parent: 41876c8d7783]