mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-10-06 14:47:10 +02:00
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
This commit is contained in:
parent
ae1c1d84ea
commit
25b13721d4
@ -3184,6 +3184,17 @@ include_dir 'conf.d'
|
||||
to <literal>replica</literal> or higher to allow replication slots to
|
||||
be used.
|
||||
</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>
|
||||
|
||||
|
@ -577,11 +577,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
|
||||
|
Loading…
Reference in New Issue
Block a user