summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian2025-11-14 02:35:28 +0000
committerBruce Momjian2025-11-14 02:35:28 +0000
commitada78cd7f80a818de1924180ff5a0647cf59ccfb (patch)
tree748eec5be512d5f12841eb58d627124d37cb404d
parenta5b69e30731fb623715ecf4c8073c0f2dee41678 (diff)
doc: clarify "logical" replication slotsHEADmaster
Also mention that logical replication slots are created by default when subscriptions are created. This should clarify the text. Backpatch-through: master
-rw-r--r--doc/src/sgml/logical-replication.sgml15
1 files changed, 8 insertions, 7 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index aff4ef5bfa2..7bbd4517744 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -225,8 +225,9 @@
</para>
<para>
- Each subscription will receive changes via one replication slot (see
- <xref linkend="streaming-replication-slots"/>). Additional replication
+ By default a new subscription creates a logical replication slot and
+ then receives changes via this slot (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
synchronization.
@@ -288,11 +289,11 @@
</para>
<sect2 id="logical-replication-subscription-slot">
- <title>Replication Slot Management</title>
+ <title>Logical Replication Slot Management</title>
<para>
As mentioned earlier, each (active) subscription receives changes from a
- replication slot on the remote (publishing) side.
+ logical replication slot on the remote (publishing) side.
</para>
<para>
Additional table synchronization slots are normally transient, created
@@ -303,7 +304,7 @@
Table <parameter>relid</parameter>, system identifier <parameter>sysid</parameter>)
</para>
<para>
- Normally, the remote replication slot is created automatically when the
+ Normally, the remote logical replication slot is created automatically when the
subscription is created using <link linkend="sql-createsubscription">
<command>CREATE SUBSCRIPTION</command></link> and it
is dropped automatically when the subscription is dropped using
@@ -538,12 +539,12 @@
</sect2>
<sect2 id="logical-replication-subscription-examples-deferred-slot">
- <title>Examples: Deferred Replication Slot Creation</title>
+ <title>Examples: Deferred Logical Replication Slot Creation</title>
<para>
There are some cases (e.g.
<xref linkend="logical-replication-subscription-slot"/>) where, if the
- remote replication slot was not created automatically, the user must create
+ remote logical replication slot was not created automatically, the user must create
it manually before the subscription can be activated. The steps to create
the slot and activate the subscription are shown in the following examples.
These examples specify the standard logical decoding output plugin