From cf54e04b9e29a13c5e7c2386c5e2ff785e830414 Mon Sep 17 00:00:00 2001 From: Amit Kapila Date: Mon, 1 Mar 2021 08:23:41 +0530 Subject: [PATCH] Update docs of logical replication for commit ce0fdbfe97. Forgot to update the logical replication configuration settings page. After commit ce0fdbfe97, table synchronization workers also started using replication origins to track the progress and the same should be reflected in docs. Author: Amit Kapila Discussion: https://postgr.es/m/CAA4eK1KkbppndxxRKbaT2sXrLkdPwy44F4pjEZ0EDrVjD9MPjQ@mail.gmail.com --- doc/src/sgml/logical-replication.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index d0742f2c52..9cd3f3fbb3 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -604,10 +604,10 @@ The subscriber also requires the max_replication_slots to be set. In this case it should be set to at least the number of - subscriptions that will be added to the subscriber. - max_logical_replication_workers must be set to at - least the number of subscriptions, again plus some reserve for the table - synchronization. Additionally the max_worker_processes + subscriptions that will be added to the subscriber, plus some reserve for + table synchronization. max_logical_replication_workers + must be set to at least the number of subscriptions, again plus some reserve + for the table synchronization. Additionally the max_worker_processes may need to be adjusted to accommodate for replication workers, at least (max_logical_replication_workers + 1). Note that some extensions and parallel queries