From 0ddc9b8bbfb52a950061768ffdea34101f3437ad Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Tue, 10 Mar 2020 13:54:27 +0900
Subject: [PATCH] doc: move database permission configuration to separate file

---
 doc/configuration-permissions.xml | 18 ++++++++++++++++++
 doc/configuration.xml             | 19 +------------------
 doc/filelist.xml                  |  1 +
 3 files changed, 20 insertions(+), 18 deletions(-)
 create mode 100644 doc/configuration-permissions.xml

diff --git a/doc/configuration-permissions.xml b/doc/configuration-permissions.xml
new file mode 100644
index 00000000..6d6e2619
--- /dev/null
+++ b/doc/configuration-permissions.xml
@@ -0,0 +1,18 @@
+<sect1 id="configuration-permissions" xreflabel="Database user permissions">
+  <title>repmgr database user permissions</title>
+
+  <indexterm>
+    <primary>configuration</primary>
+    <secondary>database user permissions</secondary>
+  </indexterm>
+
+  <para>
+    &repmgr; will create an extension database containing objects
+    for administering &repmgr; metadata. The user defined in the <varname>conninfo</varname>
+    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 <literal>--superuser</literal> when registering a &repmgr; node.
+  </para>
+</sect1>
diff --git a/doc/configuration.xml b/doc/configuration.xml
index dd952ded..fe94919d 100644
--- a/doc/configuration.xml
+++ b/doc/configuration.xml
@@ -318,23 +318,6 @@
   &configuration-file-optional-settings;
   &configuration-file-log-settings;
   &configuration-file-service-commands;
+  &configuration-permissions;
 
-  <sect1 id="configuration-permissions" xreflabel="Database user permissions">
-    <title>repmgr database user permissions</title>
-
-    <indexterm>
-      <primary>configuration</primary>
-      <secondary>database user permissions</secondary>
-    </indexterm>
-
-    <para>
-      &repmgr; will create an extension database containing objects
-      for administering &repmgr; metadata. The user defined in the <varname>conninfo</varname>
-      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 <literal>--superuser</literal> when registering a &repmgr; node.
-    </para>
-  </sect1>
 </chapter>
diff --git a/doc/filelist.xml b/doc/filelist.xml
index 1226344b..e629d01f 100644
--- a/doc/filelist.xml
+++ b/doc/filelist.xml
@@ -21,6 +21,7 @@
 <!ENTITY configuration-file-optional-settings      SYSTEM "configuration-file-optional-settings.xml">
 <!ENTITY configuration-file-log-settings      SYSTEM "configuration-file-log-settings.xml">
 <!ENTITY configuration-file-service-commands   SYSTEM "configuration-file-service-commands.xml">
+<!ENTITY configuration-permissions   SYSTEM "configuration-permissions.xml">
 <!ENTITY cloning-standbys  SYSTEM "cloning-standbys.xml">
 <!ENTITY promoting-standby  SYSTEM "promoting-standby.xml">
 <!ENTITY follow-new-primary  SYSTEM "follow-new-primary.xml">