mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
doc: clarifications for upgrade process
This commit is contained in:
@@ -71,6 +71,12 @@
|
||||
<secondary>minor release</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
A minor release upgrade involves updating &repmgr; from one minor release to another
|
||||
minor release within the same major release (e.g. <literal>5.3.1</literal> to <literal>5.3.2</literal>).
|
||||
An upgrade between minor releases of differing major releases (e.g. <literal>5.2.1</literal> to <literal>5.3.2</literal>)
|
||||
is a <link linkend="upgrading-major-version">major upgrade</link>.
|
||||
</para>
|
||||
<para>
|
||||
The process for installing minor version upgrades is quite straightforward:
|
||||
|
||||
@@ -105,15 +111,17 @@
|
||||
</para>
|
||||
|
||||
<para>
|
||||
A PostgreSQL restart is <emphasis>not</emphasis> required for minor version upgrades.
|
||||
A PostgreSQL restart is usually <emphasis>not</emphasis> required for minor version upgrades
|
||||
within the same major version (e.g. <literal>5.3.1</literal> to <literal>5.3.2</literal>).
|
||||
Be sure to check the <link linkend="appendix-release-notes">release notes</link>.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
The same &repmgr; "major version" (e.g. <literal>4.2</literal>) must be
|
||||
The same &repmgr; "major version" (e.g. <literal>5.3</literal>) must be
|
||||
installed on all nodes in the replication cluster. While it's possible to have differing
|
||||
&repmgr; "minor versions" (e.g. <literal>4.2.1</literal>) on different nodes,
|
||||
we strongly recommend updating all nodes to the latest minor version.
|
||||
&repmgr; "minor versions" (e.g. <literal>5.3.1</literal> and <literal>5.3.2</literal>)
|
||||
on different nodes, we strongly recommend updating all nodes to the latest minor version.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user