postgres
diff --git a/‎doc/src/sgml/config.sgml
Copy file name to clipboardExpand all lines: doc/src/sgml/config.sgml
+11Lines changed: 11 additions & 0 deletions b/‎doc/src/sgml/config.sgml
Copy file name to clipboardExpand all lines: doc/src/sgml/config.sgml
+11Lines changed: 11 additions & 0 deletions
diff --git a/‎doc/src/sgml/logical-replication.sgml
Copy file name to clipboardExpand all lines: doc/src/sgml/logical-replication.sgml
+5-5Lines changed: 5 additions & 5 deletions b/‎doc/src/sgml/logical-replication.sgml
Copy file name to clipboardExpand all lines: doc/src/sgml/logical-replication.sgml
+5-5Lines changed: 5 additions & 5 deletions
@@ -3891,6 +3891,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>
 
 
@@ -588,11 +588,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