From b4b8efbd3826ac0af2d1c2e7c40fcf80a4bfba45 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:03 +0200 Subject: Adding upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/logical-replication-architecture.html | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'doc/src/sgml/html/logical-replication-architecture.html') diff --git a/doc/src/sgml/html/logical-replication-architecture.html b/doc/src/sgml/html/logical-replication-architecture.html index be23888..4b74167 100644 --- a/doc/src/sgml/html/logical-replication-architecture.html +++ b/doc/src/sgml/html/logical-replication-architecture.html @@ -1,5 +1,5 @@ -31.7. Architecture

31.7. Architecture

+31.7. Architecture

31.7. Architecture

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 (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. -

\ No newline at end of file +

\ No newline at end of file -- cgit v1.2.3