From b4b8efbd3826ac0af2d1c2e7c40fcf80a4bfba45 Mon Sep 17 00:00:00 2001
From: Daniel Baumann
+
Logical replication starts by copying a snapshot of the data on the
publisher database. Once that is done, changes on the publisher are sent
to the subscriber as they occur in real time. The subscriber applies data
@@ -12,7 +12,8 @@
implemented by “walsender” and “apply”
processes. The walsender process starts logical decoding (described
in Chapter 49) of the WAL and loads the standard
- logical decoding plugin (pgoutput). The plugin transforms the changes read
+ logical decoding output plugin (31.7. Architecture
31.7. Architecture
pgoutput
). The plugin
+ transforms the changes read
from WAL to the logical replication protocol
(see Section 55.5) and filters the data
according to the publication specification. The data is then continuously
@@ -51,4 +52,4 @@
The publication publish
parameter only affects what
DML operations will be replicated. The initial data synchronization does
not take this parameter into account when copying the existing table data.
-