postgres.git / summary / log / commit / refs
commit c267ca682803f8ca233076d216fba18b635238a6
Author: Amit Kapila <akapila@postgresql.org>
Date: Wed Mar 03 05:00:27 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 ffe9f2d2877..da323621b53 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -3781,6 +3781,17 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
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>
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index c9a3c6fbcb4..43b7e824cb6 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -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
[parent: f927767919e8]