github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-25 16:16:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

doc: clarify database user permission requirements

Browse Source
This commit is contained in:
Ian Barwick
2020-03-10 14:25:26 +09:00
parent d021810ce6
commit cc233c90e8
1 changed files with 14 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
doc/configuration-permissions.xml
View File

@@ -7,12 +7,19 @@
</indexterm> </indexterm>
<para> <para>
&repmgr; will create an extension database containing objects &repmgr; requires that the database defined in the <varname>conninfo</varname>
for administering &repmgr; metadata. The user defined in the <varname>conninfo</varname> setting contains the <literal>repmgr</literal> extension. The database user defined in the
setting must be able to access all objects. Additionally, superuser permissions <varname>conninfo</varname> setting must be able to access this database and
are required to install the &repmgr; extension. The easiest way to do this the database objects contained within the extension.
is create the &repmgr; user as a superuser, however if this is not </para>
desirable, the &repmgr; user can be created as a normal user and a <para>
superuser specified with <literal>--superuser</literal> when registering a &repmgr; node. The <literal>repmgr</literal> extension can only be installed by a superuser.
If the &repmgr; user is a superuser, &repmgr; will create the extension automatically.
</para>
<para>
Alternatively, the extension can be created manually by a superuser
(with &quot;<command>CREATE EXTENSION repmgr</command>&quot;) before executing
<link linkend="repmgr-primary-register">repmgr primary register</link>.
</para> </para>
</sect1> </sect1>