database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-18 02:02:55 +03:00
Code Activity

doc: clarify "logical" replication slots

Browse Source 
Also mention that logical replication slots are created by default when
subscriptions are created.  This should clarify the text.

Backpatch-through: master
This commit is contained in:
Bruce Momjian
2025-11-13 21:35:28 -05:00
parent a5b69e3073
commit ada78cd7f8
1 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
doc/src/sgml/logical-replication.sgml
View File

@@ -225,8 +225,9 @@
</para> </para>
<para> <para>
Each subscription will receive changes via one replication slot (see By default a new subscription creates a logical replication slot and
<xref linkend="streaming-replication-slots"/>). Additional replication then receives changes via this slot (see <xref
linkend="streaming-replication-slots"/>). Additional replication
slots may be required for the initial data synchronization of slots may be required for the initial data synchronization of
pre-existing table data and those will be dropped at the end of data pre-existing table data and those will be dropped at the end of data
synchronization. synchronization.
@@ -288,11 +289,11 @@
</para> </para>
<sect2 id="logical-replication-subscription-slot"> <sect2 id="logical-replication-subscription-slot">
<title>Replication Slot Management</title> <title>Logical Replication Slot Management</title>
<para> <para>
As mentioned earlier, each (active) subscription receives changes from a 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>
<para> <para>
Additional table synchronization slots are normally transient, created Additional table synchronization slots are normally transient, created
@@ -303,7 +304,7 @@
Table <parameter>relid</parameter>, system identifier <parameter>sysid</parameter>) Table <parameter>relid</parameter>, system identifier <parameter>sysid</parameter>)
</para> </para>
<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"> subscription is created using <link linkend="sql-createsubscription">
<command>CREATE SUBSCRIPTION</command></link> and it <command>CREATE SUBSCRIPTION</command></link> and it
is dropped automatically when the subscription is dropped using is dropped automatically when the subscription is dropped using
@@ -538,12 +539,12 @@
</sect2> </sect2>
<sect2 id="logical-replication-subscription-examples-deferred-slot"> <sect2 id="logical-replication-subscription-examples-deferred-slot">
<title>Examples: Deferred Replication Slot Creation</title> <title>Examples: Deferred Logical Replication Slot Creation</title>
<para> <para>
There are some cases (e.g. There are some cases (e.g.
<xref linkend="logical-replication-subscription-slot"/>) where, if the <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 it manually before the subscription can be activated. The steps to create
the slot and activate the subscription are shown in the following examples. the slot and activate the subscription are shown in the following examples.
These examples specify the standard logical decoding output plugin These examples specify the standard logical decoding output plugin