From ec41ab8554c57c8adde4dc56f5b8441eca458bda Mon Sep 17 00:00:00 2001 From: Emre Hasegeli Date: Mon, 20 Mar 2023 17:02:45 +0100 Subject: [PATCH v13] doc: Clarify pgoutput options Author: Emre Hasegeli Reviewed-by: Peter Smith Reviewed-by: Amit Kapila Backpatch-through: 12 Discussion: https://www.postgresql.org/message-id/flat/CAE2gYzwdwtUbs-tPSV-QBwgTubiyGD2ZGsSnAVsDfAGGLDrGOA%40mail.gmail.com --- doc/src/sgml/logical-replication.sgml | 3 ++- doc/src/sgml/protocol.sgml | 11 +++++++++-- 2 files changed, 11 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index 1ac374ce40..77c7404568 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -435,21 +435,22 @@ transactional consistency is guaranteed for the publications within any single subscription. Logical replication is built with an architecture similar to physical streaming replication (see ). It is implemented by walsender and apply processes. The walsender process starts logical decoding (described in ) 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 ) and filters the data according to the publication specification. The data is then continuously transferred using the streaming replication protocol to the apply worker, which maps the data to local tables and applies the individual changes as they are received, in correct transactional order. The apply process on the subscriber database always runs with diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index 8670230d48..4c6984c718 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -2856,26 +2856,32 @@ The commands accepted in replication mode are: flow started by the START_REPLICATION SLOT slot_name LOGICAL replication command. The logical streaming replication protocol builds on the primitives of the physical streaming replication protocol. + + PostgreSQL logical decoding supports output + plugins. pgoutput is the standard one used for + the built-in logical replication. + + Logical Streaming Replication Parameters - The logical replication START_REPLICATION command - accepts following parameters: + Using the START_REPLICATION command, + pgoutput accepts the following options: proto_version Protocol version. Currently only version 1 is supported. @@ -2885,20 +2891,21 @@ The commands accepted in replication mode are: publication_names Comma separated list of publication names for which to subscribe (receive changes). The individual publication names are treated as standard objects names and can be quoted the same as needed. + At least one publication name is required. Logical Replication Protocol Messages -- 2.39.3 (Apple Git-145)