github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-22 22:56:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

doc: fold putative 4.3.1 release notes into 4.4

Browse Source
This commit is contained in:
Ian Barwick
2019-05-23 09:03:18 +09:00
parent 3c8bab97d8
commit 2bce1b371c
2 changed files with 56 additions and 77 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
HISTORY
View File

@@ -10,14 +10,12 @@
to its advertised upstream node
repmgr: prevent a standby being cloned from a witness server (Ian)
repmgrd: monitor standbys attached to primary (Ian)
general: documentation converted to DocBook XML format (Ian)
4.3.1 2019-??-??
repmgr: ensure BDR2-specific functionality cannot be used on
BDR3 and later (Ian)
repmgr: improve "--dry-run" behaviour in barman mode (Ian)
repmgr: fix data directory permissions issue in barman mode where
an existing directory is being overwritten (Ian)
general: documentation converted to DocBook XML format (Ian)
4.3 2019-04-02
repmgr: add "daemon (start|stop)" command; GitHub #528 (Ian)

129
doc/appendix-release-notes.xml
View File

@@ -25,6 +25,39 @@
<para>
<itemizedlist>
<listitem>
<para>
&repmgr;: when executing <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>,
if <option>--siblings-follow</option> is not supplied, list all nodes which repmgr considers
to be siblings (this will include the witness server, if in use), and
which will remain attached to the old primary.
</para>
</listitem>
<listitem>
<para>
&repmgr;: when executing <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>,
ignore nodes which are unreachable and marked as inactive.
Previously it would abort if any node was unreachable,
as that means it was unable to check if repmgrd is running.
</para>
<para>
However if the node has been marked as inactive in the repmgr metadata, it's
reasonable to assume the node is no longer part of the replication cluster
and does not need to be checked.
</para>
</listitem>
<listitem>
<para>
<link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>
and <link linkend="repmgr-standby-promote"><command>repmgr standby promote</command></link>:
when executing with the <option>--dry-run</option>, continue checks as far as possible
even if errors are encountered.
</para>
</listitem>
<listitem>
<para>
<link linkend="repmgr-standby-promote"><command>repmgr standby promote</command></link>: add <option>--siblings-follow</option> (similar to
@@ -121,80 +154,6 @@
</para>
</sect2>
<sect2>
<title>Other</title>
<para>
<itemizedlist>
<listitem>
<para>
The &repmgr; documentation has been converted to DocBook XML format,
as currently used by the main PostgreSQL project.
This means it can now be built against any PostgreSQL version from 9.5
(previously it was not possible to build the documentation against
PostgreSQL 10 or later), and makes it easier to provide the documentation
in other formats such as PDF.
</para>
<para>
For further details see: <xref linkend="installation-build-repmgr-docs"/>
</para>
</listitem>
</itemizedlist>
</para>
</sect2>
</sect1>
<sect1 id="release-4.3.1">
<title>Release 4.3.1</title>
<para><emphasis>???</emphasis></para>
<para>
&repmgr; 4.3.1 will be a minor release. Note that the changes listed here
are listed for inclusion in a potential 4.3.1 release, but it is not yet
certain whether this will take place, in which case all changes will
be folded into the &repmgr; 4.4 release.
</para>
<sect2>
<title>repmgr client enhancements</title>
<para>
<itemizedlist>
<listitem>
<para>
&repmgr;: when executing <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>,
if <option>--siblings-follow</option> is not supplied, list all nodes which repmgr considers
to be siblings (this will include the witness server, if in use), and
which will remain attached to the old primary.
</para>
</listitem>
<listitem>
<para>
&repmgr;: when executing <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>,
ignore nodes which are unreachable and marked as inactive.
Previously it would abort if any node was unreachable,
as that means it was unable to check if repmgrd is running.
</para>
<para>
However if the node has been marked as inactive in the repmgr metadata, it's
reasonable to assume the node is no longer part of the replication cluster
and does not need to be checked.
</para>
</listitem>
<listitem>
<para>
<link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>
and <link linkend="repmgr-standby-promote"><command>repmgr standby promote</command></link>:
when executing with the <option>--dry-run</option>, continue checks as far as possible
even if errors are encountered.
</para>
</listitem>
</itemizedlist>
</para>
</sect2>
<sect2>
<title>Bug fixes</title>
<para>
@@ -244,8 +203,30 @@
</para>
</sect2>
<sect2>
<title>Other</title>
<para>
<itemizedlist>
<listitem>
<para>
The &repmgr; documentation has been converted to DocBook XML format,
as currently used by the main PostgreSQL project.
This means it can now be built against any PostgreSQL version from 9.5
(previously it was not possible to build the documentation against
PostgreSQL 10 or later), and makes it easier to provide the documentation
in other formats such as PDF.
</para>
<para>
For further details see: <xref linkend="installation-build-repmgr-docs"/>
</para>
</listitem>
</itemizedlist>
</para>
</sect2>
</sect1>
<sect1 id="release-4.3">
<title>Release 4.3</title>
<para><emphasis>Tue April 2, 2019</emphasis></para>