From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 14 Nov 2025 15:45:59 +0000 (-0500)
Subject: doc:  clarify that logical slots track transaction activity
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=4c00960772237325bcdf75f1a068c712e392a69b;p=users%2Frhaas%2Fpostgres.git

doc:  clarify that logical slots track transaction activity

Previously it only mentioned WAL retention.

Discussion: https://postgr.es/m/pexmenhqptw5h4ma4qasz3cvjtynivxprqifgghdjtmkxdig2g@djg7bk2p6pts

Backpatch-through: master
---

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index 8a9674bd6d..aa013f348d 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -225,8 +225,9 @@
   </para>
 
   <para>
-   By default a new subscription creates a logical replication slot on the
-   publisher and then uses this slot to preserve necessary WAL (see <xref
+   By default a new subscription creates a logical replication slot on
+   the publisher and then uses this slot to track relevant transaction
+   activity and preserve necessary WAL (see <xref
    linkend="streaming-replication-slots"/>).  Additional replication
    slots may be required for the initial data synchronization of
    pre-existing table data and those will be dropped at the end of data