From 7e5609ae49732543f603dfbe868e426e7ef26f4d Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Wed, 29 Dec 2021 16:17:26 -0600 Subject: [PATCH 11/33] add missing THE.. See: 49c0864d7ef5227faa24f903902db90e5c9d5d69, 0cc59cc1f38d91587d52b14789e20bdd4c1af70a --- doc/src/sgml/protocol.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index 7e59edb1cc5..890b7a58a4b 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -2155,7 +2155,7 @@ The commands accepted in replication mode are: streaming starts on timeline tli; otherwise, the server's current timeline is selected. The server can reply with an error, for example if the requested section of WAL has already - been recycled. On success, server responds with a CopyBothResponse + been recycled. On success, the server responds with a CopyBothResponse message, and then starts to stream WAL to the frontend. @@ -2516,7 +2516,7 @@ The commands accepted in replication mode are: The server can reply with an error, for example if the - slot does not exist. On success, server responds with a CopyBothResponse + slot does not exist. On success, the server responds with a CopyBothResponse message, and then starts to stream WAL to the frontend. @@ -6639,7 +6639,7 @@ not line breaks. This section describes the detailed format of each logical replication message. These messages are either returned by the replication slot SQL -interface or are sent by a walsender. In the case of a walsender they are +interface or are sent by a walsender. In the case of a walsender, they are encapsulated inside replication protocol WAL messages as described in , and generally obey the same message flow as physical replication. -- 2.17.1