diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 2485e6190d..80d1679b14 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -3074,7 +3074,19 @@ include_dir 'conf.d'
(as shown by a state of streaming in the
pg_stat_replication> view).
- Specifying more than one standby names can allow very high availability.
+ Specifying more than one synchronous standby can allow for very high
+ availability and protection against data loss.
+
+
+ The name of a standby server for this purpose is the
+ application_name> setting of the standby, as set in the
+ standby's connection information. In case of a physical replication
+ standby, this should be set in the primary_conninfo>
+ setting in recovery.conf; the default
+ is walreceiver. For logical replication, this can
+ be set in the connection information of the subscription, and it
+ defaults to the subscription name. For other replication stream
+ consumers, consult their documentation.
This parameter specifies a list of standby servers using
@@ -3136,15 +3148,12 @@ ANY num_sync ( Basic Configuration
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index fa8ae536d9..6576272458 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -184,6 +184,14 @@
of pre-existing table data.
+
+ A logical replication subscription can be a standby for synchronous
+ replication (see ). The standby
+ name is by default the subscription name. An alternative name can be
+ specified as application_name in the connection
+ information of the subscription.
+
+
Subscriptions are dumped by pg_dump if the current user
is a superuser. Otherwise a warning is written and subscriptions are