Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit c267ca6

Browse files
author
Amit Kapila
committed
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
1 parent f927767 commit c267ca6

File tree

2 files changed

+16
-5
lines changed

2 files changed

+16
-5
lines changed

doc/src/sgml/config.sgml

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3781,6 +3781,17 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
37813781
to <literal>replica</literal> or higher to allow replication slots to
37823782
be used.
37833783
</para>
3784+
3785+
<para>
3786+
On the subscriber side, specifies how many replication origins (see
3787+
<xref linkend="replication-origins"/>) can be tracked simultaneously,
3788+
effectively limiting how many logical replication subscriptions can
3789+
be created on the server. Setting it a lower value than the current
3790+
number of tracked replication origins (reflected in
3791+
<link linkend="view-pg-replication-origin-status">pg_replication_origin_status</link>,
3792+
not <link linkend="catalog-pg-replication-origin">pg_replication_origin</link>)
3793+
will prevent the server from starting.
3794+
</para>
37843795
</listitem>
37853796
</varlistentry>
37863797

doc/src/sgml/logical-replication.sgml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -577,11 +577,11 @@
577577

578578
<para>
579579
The subscriber also requires the <varname>max_replication_slots</varname>
580-
to be set. In this case it should be set to at least the number of
581-
subscriptions that will be added to the subscriber.
582-
<varname>max_logical_replication_workers</varname> must be set to at
583-
least the number of subscriptions, again plus some reserve for the table
584-
synchronization. Additionally the <varname>max_worker_processes</varname>
580+
be set to configure how many replication origins can be tracked. In this
581+
case it should be set to at least the number of subscriptions that will be
582+
added to the subscriber. <varname>max_logical_replication_workers</varname>
583+
must be set to at least the number of subscriptions, again plus some reserve
584+
for the table synchronization. Additionally the <varname>max_worker_processes</varname>
585585
may need to be adjusted to accommodate for replication workers, at least
586586
(<varname>max_logical_replication_workers</varname>
587587
+ <literal>1</literal>). Note that some extensions and parallel queries

0 commit comments

Comments
 (0)