mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-23 07:06:30 +00:00
8b059bc9b0
Default was previously NOTICE (as in repmgr 3.x) but documentation implied it was INFO, and many of the the documentation examples assume it is. This produces some quite informative log output, without creating excessive log file volume. In particular it's useful to get a better idea of what repmgrd is actually doing. Also add documentation section for the log configuration parameters. GitHub #470, containing change suggested in GitHub #467.
27 lines
1.1 KiB
Plaintext
27 lines
1.1 KiB
Plaintext
<chapter id="configuration" xreflabel="Configuration">
|
|
<title>repmgr configuration</title>
|
|
|
|
&configuration-file;
|
|
&configuration-file-required-settings;
|
|
&configuration-file-log-settings;
|
|
&configuration-file-service-commands;
|
|
|
|
<sect1 id="configuration-permissions" xreflabel="Database user permissions">
|
|
<indexterm>
|
|
<primary>configuration</primary>
|
|
<secondary>database user permissions</secondary>
|
|
</indexterm>
|
|
|
|
<title>repmgr database user permissions</title>
|
|
<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>
|