From c03c509e7308ac8a066ce846583b712df6047501 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Thu, 26 Oct 2017 16:11:17 +0900 Subject: [PATCH] docs: update configuration documentation --- doc/configuration-file.sgml | 5 +++++ doc/configuration.sgml | 19 ++++++++++++++++++- 2 files changed, 23 insertions(+), 1 deletion(-) diff --git a/doc/configuration-file.sgml b/doc/configuration-file.sgml index 6b097e72..533ccfc3 100644 --- a/doc/configuration-file.sgml +++ b/doc/configuration-file.sgml @@ -4,6 +4,11 @@ location + + configuration + repmgr.conf location + + Configuration file location repmgr and repmgrd diff --git a/doc/configuration.sgml b/doc/configuration.sgml index 5ee77f07..ffd4e53e 100644 --- a/doc/configuration.sgml +++ b/doc/configuration.sgml @@ -1,7 +1,24 @@ - repmgr configuration + repmgr configuration &configuration-file; &configuration-file-settings; + + + configuration + user permissions + + + repmgr user permissions + + &repmgr; will create an extension in the BDR database containing objects + for administering &repmgr; metadata. The user defined in the `conninfo` + setting must be able to access all objects. Additionally, superuser permissions + are required to install the &repmgr; extension. The easiest way to do this + is create the &repmgr; user as a superuser, however if this is not + desirable, the &repmgr; user can be created as a normal user and a + superuser specified with --superuser when registering a BDR node. + +