mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
standby clone: rename --recovery-conf-only to --replication-conf-only
A more generic option name to cover pre- and post-Pg12 replication configuration methods. --recovery-conf-only is retained as an alias for backwards compatibility.
This commit is contained in:
@@ -17,6 +17,36 @@
|
||||
|
||||
<!-- remember to update the release date in ../repmgr_version.h.in -->
|
||||
|
||||
<sect1 id="release-5.1.0">
|
||||
<title>Release 5.1.0</title>
|
||||
<para><emphasis>?? ?? ??, 20??</emphasis></para>
|
||||
|
||||
<para>
|
||||
&repmgr; 5.1.0 is a major release.
|
||||
</para>
|
||||
<para>
|
||||
For details on how to upgrade an existing &repmgr; installation, see
|
||||
documentation section <link linkend="upgrading-major-version">Upgrading a major version release</link>.
|
||||
</para>
|
||||
<para>
|
||||
If &repmgrd; is in use, a PostgreSQL restart <emphasis>is</emphasis> required;
|
||||
in that case we suggest combining this &repmgr; upgrade with the next PostgreSQL
|
||||
minor release, which will require a PostgreSQL restart in any case.
|
||||
</para>
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>Compatibility changes</title>
|
||||
<para>
|
||||
The <link linkend="repmgr-standby-clone"><command>repmgr standby clone</command></link>
|
||||
<option>--recovery-conf-only</option> option has been renamed to
|
||||
<option>--replication-conf-only</option>. <option>--recovery-conf-only</option> will
|
||||
still be accepted as an alias.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="release-5.0">
|
||||
<title id="release-current">Release 5.0</title>
|
||||
<para><emphasis>Tue 15 October, 2019</emphasis></para>
|
||||
|
||||
Reference in New Issue
Block a user