From 2bce1b371c6302516253f98864fa1b740b27f8ed Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Thu, 23 May 2019 09:03:18 +0900 Subject: [PATCH] doc: fold putative 4.3.1 release notes into 4.4 --- HISTORY | 4 +- doc/appendix-release-notes.xml | 129 ++++++++++++++------------------- 2 files changed, 56 insertions(+), 77 deletions(-) diff --git a/HISTORY b/HISTORY index 412b422d..fe6d96a6 100644 --- a/HISTORY +++ b/HISTORY @@ -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) diff --git a/doc/appendix-release-notes.xml b/doc/appendix-release-notes.xml index d354d656..3f30b0f0 100644 --- a/doc/appendix-release-notes.xml +++ b/doc/appendix-release-notes.xml @@ -25,6 +25,39 @@ + + + &repmgr;: when executing repmgr standby switchover, + if 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. + + + + + + &repmgr;: when executing repmgr standby switchover, + 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. + + + 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. + + + + + + repmgr standby switchover + and repmgr standby promote: + when executing with the , continue checks as far as possible + even if errors are encountered. + + + + repmgr standby promote: add (similar to @@ -121,80 +154,6 @@ - - Other - - - - - 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. - - - For further details see: - - - - - - - - - Release 4.3.1 - ??? - - - &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. - - - - repmgr client enhancements - - - - - &repmgr;: when executing repmgr standby switchover, - if 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. - - - - - - &repmgr;: when executing repmgr standby switchover, - 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. - - - 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. - - - - - - repmgr standby switchover - and repmgr standby promote: - when executing with the , continue checks as far as possible - even if errors are encountered. - - - - - - - - Bug fixes @@ -244,8 +203,30 @@ + + + Other + + + + + 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. + + + For further details see: + + + + + + Release 4.3 Tue April 2, 2019