From 96acd3f915b2ca4ed3db1f1ebd3fab31e9032ae4 Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Mon, 20 Apr 2020 15:34:29 +0900
Subject: [PATCH] doc: clarify .pgpass usage with -S/--superuser option

---
 doc/configuration-password-management.xml | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/doc/configuration-password-management.xml b/doc/configuration-password-management.xml
index 2a535996..e7907165 100644
--- a/doc/configuration-password-management.xml
+++ b/doc/configuration-password-management.xml
@@ -127,8 +127,21 @@ node2:5432:repmgr:repmgr:foo
 node2:5432:replication:repluser:foo
 node3:5432:repmgr:repmgr:foo
 node3:5432:replication:repluser:foo</programlisting>
-
+      If you are planning to use the <option>-S</option>/<option>--superuser</option> option,
+      there must also be an entry enabling the superuser to connect to the &repmgr; database.
+      Assuming the superuser is <literal>postgres</literal>, the file would look like this:
+        <programlisting>
+node1:5432:repmgr:repmgr:foo
+node1:5432:repmgr:postgres:foo
+node1:5432:replication:repluser:foo
+node2:5432:repmgr:repmgr:foo
+node2:5432:repmgr:postgres:foo
+node2:5432:replication:repluser:foo
+node3:5432:repmgr:repmgr:foo
+node3:5432:repmgr:postgres:foo
+node3:5432:replication:repluser:foo</programlisting>
     </para>
+
     <note>
       <para>
         It's possible to specify an alternative location for the <filename>~/.pgpass</filename> file, either via