From 285ecb5f14e20acf889938be2e4804c26f0e1deb Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Thu, 18 Feb 2021 10:08:27 -0600 Subject: [PATCH 19/21] doc review: Multiple xacts during table sync in logical replication ce0fdbfe9722867b7fad4d3ede9b6a6bfc51fb4e --- doc/src/sgml/logical-replication.sgml | 4 ++-- doc/src/sgml/ref/alter_subscription.sgml | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index d0742f2c52..69a9768504 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -490,9 +490,9 @@ any changes that happened during the initial data copy using standard logical replication. During this synchronization phase, the changes are applied and committed in the same order as they happened on the - publisher. Once the synchronization is done, the control of the + publisher. Once synchronization is done, control of the replication of the table is given back to the main apply process where - the replication continues as normal. + replication continues as normal. diff --git a/doc/src/sgml/ref/alter_subscription.sgml b/doc/src/sgml/ref/alter_subscription.sgml index bcb0acf28d..0adf68ecca 100644 --- a/doc/src/sgml/ref/alter_subscription.sgml +++ b/doc/src/sgml/ref/alter_subscription.sgml @@ -56,7 +56,7 @@ ALTER SUBSCRIPTION name RENAME TO < allocated for the subscription on the remote host are released. If due to network breakdown or some other error, PostgreSQL is unable to remove the slots, an ERROR will be reported. To proceed in this - situation, either the user need to retry the operation or disassociate the + situation, the user either needs to retry the operation or disassociate the slot from the subscription and drop the subscription as explained in . -- 2.17.0