upstream/postgresql
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-06-13 10:40:09 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: fix reference for finding replication slots to drop

Browse source 
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
This commit is contained in:
Fujii Masao 2026-06-12 11:08:33 +09:00
parent 0e47bb5fbe
commit 67bd944c0e
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/src/sgml/maintenance.sgml
View file

@ -702,20 +702,20 @@ HINT: Execute a database-wide VACUUM in that database.
<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