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

daemon (start|stop): verify that repmgrd starts/stops.

Browse Source 
Note this may not always be possible for "daemon stop" if we are unable
to determine the repmgrd PID.
This commit is contained in:
Ian Barwick
2019-01-30 14:36:52 +09:00
parent 70e4243a1d
commit d7420d7274
8 changed files with 249 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
doc/repmgr-daemon-stop.sgml
View File

@@ -24,6 +24,18 @@
local node.
</para>
<para>
By default, &repmgr; will wait for up to 15 seconds to confirm that <application>repmgrd</application>
stopped. This behaviour can be overridden by specifying a diffent value using the <option>--wait</option>
option, or disabled altogether with the <option>--no-wait</option> option.
</para>
<note>
<para>
If PostgreSQL is not running on the local node, under some circumstances &repmgr; may not
be able to confirm if <application>repmgrd</application> has actually stopped.
</para>
</note>
</refsect1>
<refsect1>
@@ -65,6 +77,32 @@
</listitem>
</varlistentry>
<varlistentry>
<term><option>-w/--wait</option></term>
<listitem>
<para>
Wait for the specified number of seconds to confirm that <application>repmgrd</application>
stopped successfully.
</para>
<para>
Note that providing <option>--wait=0</option> is the equivalent of <option>--no-wait</option>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>--no-wait</option></term>
<listitem>
<para>
Don't wait to confirm that <application>repmgrd</application>
stopped successfully.
</para>
<para>
This is equivalent to providing <option>--wait=0</option>.
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>