diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 6daf2918819..7a5d1ea903e 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -3184,6 +3184,17 @@ include_dir 'conf.d'
to replica or higher to allow replication slots to
be used.
+
+
+ On the subscriber side, specifies how many replication origins (see
+ ) 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
+ pg_replication_origin_status,
+ not pg_replication_origin)
+ will prevent the server from starting.
+
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 @@
The subscriber also requires the max_replication_slots
- to be set. In this case it should be set to at least the number of
- subscriptions that will be added to the subscriber.
- max_logical_replication_workers must be set to at
- least the number of subscriptions, again plus some reserve for the table
- synchronization. Additionally the max_worker_processes
+ 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. max_logical_replication_workers
+ must be set to at least the number of subscriptions, again plus some reserve
+ for the table synchronization. Additionally the max_worker_processes
may need to be adjusted to accommodate for replication workers, at least
(max_logical_replication_workers
+ 1). Note that some extensions and parallel queries