mirror of
https://github.com/postgres/postgres.git
synced 2025-11-18 02:02:55 +03:00
doc: remove verbiage about "receiving" data from rep. slots
The slots are just LSN markers, not something to receive from. Backpatch-through: master
This commit is contained in:
@@ -225,8 +225,8 @@
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
By default a new subscription creates a logical replication slot and
|
By default a new subscription creates a logical replication slot on the
|
||||||
then receives changes via this slot (see <xref
|
publisher and then uses this slot to preserve necessary WAL (see <xref
|
||||||
linkend="streaming-replication-slots"/>). Additional replication
|
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
|
||||||
@@ -292,8 +292,8 @@
|
|||||||
<title>Logical 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 uses a logical
|
||||||
logical replication slot on the remote (publishing) side.
|
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
|
||||||
|
|||||||
Reference in New Issue
Block a user