From 56aae22b6c846c0b081ef2ca60424bab2e5e0d1e Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Tue, 17 Sep 2019 11:00:04 +0900 Subject: [PATCH] doc: update release notes --- HISTORY | 6 +- doc/appendix-release-notes.xml | 228 ++++++++++++++++++++++----------- 2 files changed, 155 insertions(+), 79 deletions(-) diff --git a/HISTORY b/HISTORY index 6822c7bd..b78b2160 100644 --- a/HISTORY +++ b/HISTORY @@ -1,9 +1,7 @@ -5.0 2019-??-?? - general: add PostgreSQL 12 support (Ian) +5.0 2019-09-?? + general: add PostgreSQL 12 support (Ian) general: parse configuration file using flex (Ian) repmgr: rename "repmgr daemon ..." commands to "repmgr service ..." (Ian) - -4.4.1 2019-??-?? repmgr: improve data directory check (Ian) repmgr: improve extension check during "standby clone" (Ian) diff --git a/doc/appendix-release-notes.xml b/doc/appendix-release-notes.xml index b8af4cab..520915b5 100644 --- a/doc/appendix-release-notes.xml +++ b/doc/appendix-release-notes.xml @@ -19,75 +19,145 @@ Release 5.0 - ?? ???, 2019 + ?? September ??, 2019 + + + &repmgr; 5.0 is a major release. + + + For details on how to upgrade an existing &repmgr; installation, see + documentation section Upgrading a major version release. + + + If &repmgrd; is in use, a PostgreSQL restart is 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. + + Compatibility changes - - Some repmgr daemon ... commands have been renamed to - repmgr service ... as they have a cluster-wide effect - and to avoid giving the impression they affect only the local &repmgr; daemon. + + + Configuration file parsing has been made stricter + + String parameters should always be enclosed in single quotes. + + + For example, in &repmgr; 4.4 and earlier, the following repmgr.conf + entry was valid: + +conninfo=host=node1 user=repmgr dbname=repmgr connect_timeout=2 + This must now be changed to: + +conninfo='host=node1 user=repmgr dbname=repmgr connect_timeout=2' + + + Note that simple string identifiers (e.g. node_name=node1) + may remain unquoted, though we recommend always enclosing + strings in single quotes. + + + Additionally, leading/trailing white space between single quotes will no longer + be trimmed; the entire string between single quotes will be + taken literally. + + + Strings enclosed in double quotes (e.g. node_name="node1") + will now be rejected; previously they were accepted, but the double quotes were + interpreted as part of the string, which was a frequent cause of confusion. + + + This syntax matches that used by PostgreSQL itself. + + + + + Some "repmgr daemon ..." commands renamed + + + Some "repmgr daemon ..." commands have been renamed to + "repmgr service ..." as they have a cluster-wide effect + and to avoid giving the impression they affect only the local &repmgr; daemon. + + + The following commands are affected: + + + + + + repmgr daemon pause + (now repmgr service pause) + + + + + + repmgr daemon unpause + (now repmgr service unpause) + + + + + + repmgr daemon status + (now repmgr service status) + + + + + + + The "repmgr daemon ..." form will still be accepted + for backwards compatibility. + + + + + Some deprecated command line options removed + + The following command line options, which have been deprecated since &repmgr; 3.3 + (and which no longer had any effect other than to generate a warning about their use) + have been removed: + + + + + + + + + + + + + + + - - Following commands are affected: + - - - - - repmgr daemon pause - (now repmgr service pause) - - - - - - repmgr daemon unpause - (now repmgr service unpause) - - - - - - repmgr daemon status - (now repmgr service status) - - - - - - - The repmgr daemon ... form will still be accepted - for backwards compatibility. - - - - - The following command line options, which have been deprecated since &repmgr; 3.3 - (and which no longer had any effect other than to generate a warning about their use) - have been removed: - - - - - - - - - - - - - - - - General enhancements + + + Support for PostgreSQL 12 added. + + + Beginning with PostgreSQL 12, replication configuration has been integrated + into the main PostgreSQL configuraton system and the conventional + recovery.conf file is no longer valid. + + + &repmgr; has been modified to be compatible with this change. + + + @@ -100,23 +170,31 @@ This makes configuration file parsing more robust and consistent. - - - This change makes configuration file parsing somewhat stricter - than previously. When upgrading, be sure to check your - configuration file syntax. - - - - In particular, all string values containing spaces - must be contained within single quotes. - - - Additionally, leading/trailing white space between single quotes will no longer - be trimmed; the entire string between single quotes will be - taken literally. - - + + See item Configuration file parsing has been made stricter + for details. + + + + + + repmgr standby clone: + checks for availability of the &repmgr; extension on the upstream node have + been improved and error messages improved. + + + + + + + + Bug fixes + + + + + +