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 @@
- Each subscription will receive changes via one replication slot (see
- ). Additional replication
+ By default a new subscription creates a logical replication slot and
+ then receives changes via this slot (see ). 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 @@
- Replication Slot Management
+ Logical Replication Slot Management
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.
Additional table synchronization slots are normally transient, created
@@ -303,7 +304,7 @@
Table relid, system identifier sysid)
- 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
CREATE SUBSCRIPTION and it
is dropped automatically when the subscription is dropped using
@@ -538,12 +539,12 @@
- Examples: Deferred Replication Slot Creation
+ Examples: Deferred Logical Replication Slot Creation
There are some cases (e.g.
) 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