mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-25 16:16:29 +00:00
doc: note importance of installing same repmgr versions
This commit is contained in:
@@ -145,6 +145,40 @@
|
|||||||
</para>
|
</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
|
<sect2 id="faq-version-mix">
|
||||||
|
<title>Does it matter if different &repmgr; versions are present in the replication cluster?</title>
|
||||||
|
<para>
|
||||||
|
Yes. If different "major" &repmgr; versions (e.g. 3.3.x and 4.1.x) are present,
|
||||||
|
&repmgr; (in particular <application>repmgrd</application>)
|
||||||
|
may not run, or run properly, or in the worst case (if different <application>repmgrd</application>
|
||||||
|
versions are running and there are differences in the failover implementation) break
|
||||||
|
your replication cluster.
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
If different "minor" &repmgr; versions (e.g. 4.1.1 and 4.1.6) are installed,
|
||||||
|
&repmgr; will function, but we strongly recommend always running the same version
|
||||||
|
to ensure there are no unexpected suprises, e.g. a newer version behaving slightly
|
||||||
|
differently to the older version.
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
See also <link linkend="faq-upgrade-repmgr">Should I upgrade &repmgr;?</link>.
|
||||||
|
</para>
|
||||||
|
</sect2>
|
||||||
|
|
||||||
|
<sect2 id="faq-upgrade-repmgr">
|
||||||
|
<title>Should I upgrade &repmgr;?</title>
|
||||||
|
<para>
|
||||||
|
Yes.
|
||||||
|
</para>
|
||||||
|
<para>
|
||||||
|
We don't release new versions for fun, you know. Upgrading may require a little effort,
|
||||||
|
but running an older &repmgr; version with bugs which have since been fixed may end up
|
||||||
|
costing you more effort. The same applies to PostgreSQL itself.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
</sect2>
|
||||||
|
|
||||||
|
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1 id="faq-repmgr" xreflabel="repmgr">
|
<sect1 id="faq-repmgr" xreflabel="repmgr">
|
||||||
|
|||||||
@@ -36,6 +36,20 @@
|
|||||||
major version.
|
major version.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<note>
|
||||||
|
<simpara>
|
||||||
|
The same "major" &repmgr; version (e.g. <literal>4.2.x</literal>) <emphasis>must</emphasis>
|
||||||
|
be installed on all node in the replication cluster. We strongly recommend keeping all
|
||||||
|
nodes on the same (preferably latest) "minor" &repmgr; version to minimize the risk
|
||||||
|
of incompatibilities.
|
||||||
|
</simpara>
|
||||||
|
<simpara>
|
||||||
|
If different "major" &repmgr; versions (e.g. 3.3.x and 4.1.x)
|
||||||
|
are installed on different nodes, in the best case &repmgr; (in particular <application>repmgrd</application>)
|
||||||
|
will not run. In the worst case, you will end up with a broken cluster.
|
||||||
|
</simpara>
|
||||||
|
</note>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
A dedicated system user for &repmgr; is <emphasis>not</emphasis> required; as many &repmgr; and
|
A dedicated system user for &repmgr; is <emphasis>not</emphasis> required; as many &repmgr; and
|
||||||
<application>repmgrd</application> actions require direct access to the PostgreSQL data directory,
|
<application>repmgrd</application> actions require direct access to the PostgreSQL data directory,
|
||||||
|
|||||||
Reference in New Issue
Block a user