postgres.git / summary / log / commit / refs

commit    90c737669fd2ab8e02ef7e8200adbce6fccf5c65
Author:   Amit Kapila <akapila@postgresql.org>
Date:     Wed Mar 03 06:19:12 2021 +0000
First released in: 14.0, 10.17, 11.12, 12.7, 13.3

    Clarify the usage of max_replication_slots on the subscriber side.
    
    It was not clear in the docs that the max_replication_slots is also used
    to track replication origins on the subscriber side.
    
    Author: Paul Martinez
    Reviewed-by: Amit Kapila
    Backpatch-through: 10 where logical replication was introduced
    Discussion: https://postgr.es/m/CACqFVBZgwCN_pHnW6dMNCrOS7tiHCw6Retf_=U2Vvj3aUSeATw@mail.gmail.com


doc/src/sgml/config.sgml | 11 +++++++++++ doc/src/sgml/logical-replication.sgml | 10 +++++----- 2 files changed, 16 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 159aedb99ce..f1731779d8e 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -3091,6 +3091,17 @@ include_dir 'conf.d' be used. Setting it to a lower value than the number of currently existing replication slots will prevent the server from starting. </para> + + <para> + On the subscriber side, specifies how many replication origins (see + <xref linkend="replication-origins">) can be tracked simultaneously, + effectively limiting how many logical replication subscriptions can + be created on the server. Setting it a lower value than the current + number of tracked replication origins (reflected in + <link linkend="view-pg-replication-origin-status">pg_replication_origin_status</link>, + not <link linkend="catalog-pg-replication-origin">pg_replication_origin</link>) + will prevent the server from starting. + </para> </listitem> </varlistentry> diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index 6e725c5037d..b6a14a51722 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -570,11 +570,11 @@ <para> The subscriber also requires the <varname>max_replication_slots</varname> - to be set. In this case it should be set to at least the number of - subscriptions that will be added to the subscriber. - <varname>max_logical_replication_workers</varname> must be set to at - least the number of subscriptions, again plus some reserve for the table - synchronization. Additionally the <varname>max_worker_processes</varname> + be set to configure how many replication origins can be tracked. In this + case it should be set to at least the number of subscriptions that will be + added to the subscriber. <varname>max_logical_replication_workers</varname> + must be set to at least the number of subscriptions, again plus some reserve + for the table synchronization. Additionally the <varname>max_worker_processes</varname> may need to be adjusted to accommodate for replication workers, at least (<varname>max_logical_replication_workers</varname> + <literal>1</literal>). Note that some extensions and parallel queries [parent: 926139dd04bb]