doc: Improve logical replication security setup info

Reported-by: Jeff Janes <jeff.janes@gmail.com>

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index 3828624d3c1c1ca15bfd03a70bc1a3e1e90eef11..92ec175af1576bb6a2df233221f8d6d57df16517 100644 (file)
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -452,7 +452,7 @@
 
   <para>
    The role used for the replication connection must have
-   the <literal>REPLICATION</literal> attribute.  Access for the role must be
+   the <literal>REPLICATION</literal> attribute (or be a superuser).  Access for the role must be
    configured in <filename>pg_hba.conf</filename>.
   </para>
 

diff --git a/doc/src/sgml/ref/create_subscription.sgml b/doc/src/sgml/ref/create_subscription.sgml
index 3ca06fb3c356d097aeae84d8f6c63bd1aa7c80e6..9f45b6f574ac86600c726647ccc9df57be868897 100644 (file)
--- a/doc/src/sgml/ref/create_subscription.sgml
+++ b/doc/src/sgml/ref/create_subscription.sgml
@@ -222,7 +222,7 @@ CREATE SUBSCRIPTION <replaceable class="PARAMETER">subscription_name</replaceabl
   <title>Notes</title>
 
   <para>
-   See <xref linkend="streaming-replication-authentication"> for details on
+   See <xref linkend="logical-replication-security"> for details on
    how to configure access control between the subscription and the
    publication instance.
   </para>