mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-27 17:06:29 +00:00
doc: clarify prerequisites for executing the "repmgr service" commands
Note node accessibility requirements on each command's reference page.
This commit is contained in:
@@ -42,6 +42,15 @@
|
|||||||
</para>
|
</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
<refsect1>
|
||||||
|
<title>Prerequisites</title>
|
||||||
|
<para>
|
||||||
|
PostgreSQL must be accessible on all nodes (using the <varname>conninfo</varname> string shown by
|
||||||
|
<link linkend="repmgr-cluster-show"><command>repmgr cluster show</command></link>)
|
||||||
|
from the node where <command>repmgr service pause</command> is executed.
|
||||||
|
</para>
|
||||||
|
</refsect1>
|
||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>Execution</title>
|
<title>Execution</title>
|
||||||
<para>
|
<para>
|
||||||
|
|||||||
@@ -27,6 +27,15 @@
|
|||||||
</para>
|
</para>
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
<refsect1>
|
||||||
|
<title>Prerequisites</title>
|
||||||
|
<para>
|
||||||
|
PostgreSQL should be accessible on all nodes (using the <varname>conninfo</varname> string shown by
|
||||||
|
<link linkend="repmgr-cluster-show"><command>repmgr cluster show</command></link>)
|
||||||
|
from the node where <command>repmgr service status</command> is executed.
|
||||||
|
</para>
|
||||||
|
</refsect1>
|
||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>Execution</title>
|
<title>Execution</title>
|
||||||
<para>
|
<para>
|
||||||
@@ -34,9 +43,12 @@
|
|||||||
replication cluster. A valid <filename>repmgr.conf</filename> file is required.
|
replication cluster. A valid <filename>repmgr.conf</filename> file is required.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
If PostgreSQL is not running on a node, &repmgr; will not be able to determine the
|
If a node is not accessible, or PostgreSQL itself is not running on the node,
|
||||||
status of that node's &repmgrd; instance.
|
&repmgr; will not be able to determine the status of that node's &repmgrd; instance,
|
||||||
|
and "<literal>n/a</literal>" will be displayed in the node's <literal>repmgrd</literal>
|
||||||
|
column.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<note>
|
<note>
|
||||||
<para>
|
<para>
|
||||||
After restarting PostgreSQL on any node, the &repmgrd; instance
|
After restarting PostgreSQL on any node, the &repmgrd; instance
|
||||||
|
|||||||
@@ -36,6 +36,15 @@
|
|||||||
|
|
||||||
</refsect1>
|
</refsect1>
|
||||||
|
|
||||||
|
<refsect1>
|
||||||
|
<title>Prerequisites</title>
|
||||||
|
<para>
|
||||||
|
PostgreSQL must be accessible on all nodes (using the <varname>conninfo</varname> string shown by
|
||||||
|
<link linkend="repmgr-cluster-show"><command>repmgr cluster show</command></link>)
|
||||||
|
from the node where <command>repmgr service pause</command> is executed.
|
||||||
|
</para>
|
||||||
|
</refsect1>
|
||||||
|
|
||||||
<refsect1>
|
<refsect1>
|
||||||
<title>Execution</title>
|
<title>Execution</title>
|
||||||
<para>
|
<para>
|
||||||
|
|||||||
Reference in New Issue
Block a user