From 1196821457d0db16e5650d6eb27394e5dd63d5c4 Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Tue, 1 Oct 2019 10:29:44 +0900
Subject: [PATCH] doc: update FAQ

Note pg_monitor default role as well, and link to relevant section
in the PostgreSQL documentation.
---
 doc/appendix-faq.xml | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/doc/appendix-faq.xml b/doc/appendix-faq.xml
index e4adfba6..8d2a0f3c 100644
--- a/doc/appendix-faq.xml
+++ b/doc/appendix-faq.xml
@@ -199,8 +199,13 @@
         earlier, where the <literal>repmgr</literal> user is not a superuser; in that
         case the <literal>repmgr</literal> user will not be able to access the
         <literal>data_directory</literal> configuration setting, access to which is restricted
-        to superusers. (In PostgreSQL 10 and later, non-superusers can be added to the
-        group <option>pg_read_all_settings</option> which will enable them to read this setting).
+        to superusers.
+      </para>
+      <para>
+        In PostgreSQL 10 and later, non-superusers can be added to the
+        <ulink url="https://www.postgresql.org/docs/current/default-roles.html">default role</ulink>
+        <option>pg_read_all_settings</option> (or the meta-role <option>pg_monitor</option>)
+        which will enable them to read this setting.
       </para>
     </sect2>