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

doc: various improvements to repmgrd documentation

Browse Source
This commit is contained in:
Ian Barwick
2019-03-20 16:10:03 +09:00
parent 7d0caefaee
commit 5e775cef16
3 changed files with 62 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/repmgr.sgml
View File

@@ -73,7 +73,6 @@
&promoting-standby;
&follow-new-primary;
&switchover;
&configuring-witness-server;
&event-notifications;
&upgrading-repmgr;
</part>
@@ -83,6 +82,7 @@
&repmgrd-overview;
&repmgrd-automatic-failover;
&repmgrd-configuration;
&configuring-witness-server;
&repmgrd-operation;
&repmgrd-bdr;
</part>

2
doc/repmgrd-configuration.sgml
View File

@@ -53,7 +53,7 @@
</varlistentry>
<varlistentry>
<varlistentry id="connection_check_type">
<indexterm>
<primary>connection_check_type</primary>

60
doc/repmgrd-overview.sgml
View File

@@ -13,6 +13,66 @@
failover and updating standbys to follow the new primary, as well as
providing monitoring information about the state of each standby.
</para>
<para>
<application>repmgrd</application> is designed to be straightforward to set up
and does not require additional external infrastructure.
</para>
<para>
Functionality provided by <application>repmgrd</application> includes:
<itemizedlist spacing="compact" mark="bullet">
<listitem>
<simpara>
wide range of <link linkend="repmgrd-basic-configuration">configuration options</link>
</simpara>
</listitem>
<listitem>
<simpara>
option to execute custom scripts (&quot;<link linkend="event-notifications">event notifications</link>
at different points in the failover sequence
</simpara>
</listitem>
<listitem>
<simpara>
ability to <link linkend="repmgrd-pausing">pause repmgrd</link>
operation on all nodes with a
<link linkend="repmgr-daemon-pause"><command>single command</command></link>
</simpara>
</listitem>
<listitem>
<simpara>
optional <link linkend="using-witness-server">witness server</link>
</simpara>
</listitem>
<listitem>
<simpara>
&quot;location&quot; configuration option to restrict
potential promotion candidates to a single location
(e.g. when nodes are spread over multiple data centres)
</simpara>
</listitem>
<listitem>
<simpara>
<link linkend="connection_check_type">choice of method</link> to determine node availability
(PostgreSQL ping, query execution or new connection)
</simpara>
</listitem>
<listitem>
<simpara>
retention of monitoring statistics (optional)
</simpara>
</listitem>
</itemizedlist>
</para>
<sect1 id="repmgrd-demonstration">