summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian2025-11-14 15:45:59 +0000
committerBruce Momjian2025-11-14 15:45:59 +0000
commit4c00960772237325bcdf75f1a068c712e392a69b (patch)
treecf269aaf3a520c768ab74819a9a14e4a433d88ad
parent43e6929bb2945553df021874914ade88743abc1f (diff)
doc: clarify that logical slots track transaction activityHEADmaster
Previously it only mentioned WAL retention. Discussion: https://postgr.es/m/pexmenhqptw5h4ma4qasz3cvjtynivxprqifgghdjtmkxdig2g@djg7bk2p6pts Backpatch-through: master
-rw-r--r--doc/src/sgml/logical-replication.sgml5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index 8a9674bd6d1..aa013f348d4 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