From 020b5b6982a062b3669679f613e88ee301fc038f Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Tue, 21 Nov 2017 16:27:18 +0900 Subject: [PATCH] docs: update 4.0.0 release notes --- doc/appendix-release-notes.sgml | 153 ++++++++++++++++++++++++++++---- 1 file changed, 138 insertions(+), 15 deletions(-) diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml index 1b397c70..24ceea3d 100644 --- a/doc/appendix-release-notes.sgml +++ b/doc/appendix-release-notes.sgml @@ -1,4 +1,4 @@ - + Release notes Release notes @@ -16,30 +16,153 @@ See also: - - Release 4.0beta1 + + Release 4.0.0 - Thu Oct 5, 2017 + Tue Nov 21, 2017 - repmgr 4.0 is an entirely new version of &repmgr;, providing many - improvements together with some changes in the way it works. - In particular changes have been made to some configuration file - settings and command line options for consistency and clarity. + repmgr 4.0 is an entirely new version of &repmgr;, implementing &repmgr; + as a native PostgreSQL extension, adding new and improving existing features, + and making &repmgr; more user-friendly and intuitive to use. The new code base + will make it easier to add additional functionality for future releases. - - For detailed instructions on upgrading from repmgr 3.x, see - . - - - + + With the new version, the opportunity has been taken to + make some changes in the way &repmgr; is set up and + configured. In particular changes have been made to some + configuration file settings consistency for and clarity. + Changes are covered in detail below + + To standardise terminology, from this release primary is used to denote the read/write node in a streaming replication cluster. master is still accepted as an alias for &repmgr; commands (e.g. repmgr master register). - + + + + For detailed instructions on upgrading from repmgr 3.x, see . + + + + Features and improvements + + + + + + improved switchover: + the switchover process has been improved and streamlined, + speeding up the switchover process and can also instruct other standbys + to follow the new primary once the switchover has completed. See + for more details. + + + + + + "--dry-run" option: many &repmgr; commands now provide + a --dry-run option which will execute the command as far + as possible without making any changes, which will enable possible issues + to be identified before the intended operation is actually carried out. + + + + + + easier upgrades: &repmgr; is now implemented as a native + PostgreSQL extension, which means future upgrades can be carried out by + installing the upgraded package and issuing + ALTER EXTENSION repmgr UPDATE. + + + + + + + improved logging output: + &repmgr; (and repmgrd) now provide more explicit + logging output giving a better picture of what is going on. Where appropriate, + DETAIL and HINT log lines provide additional + detail and suggestions for resolving problems. Additionally, repmgrd + now emits informational log lines at regular, configurable intervals + to confirm that it's running correctly and which node(s) it's monitoring. + + + + + + automatic configuration file location in packages: + Many operating system packages place the &repmgr; configuration files + in a version-specific subdirectory, e.g. /etc/repmgr/9.6/repmgr.conf; + &repmgr; now makes it easy for package maintainers to provide a patch + with the actual file location, meaning repmgr.conf + does not need to be provided explicitly. This is currently the case + for 2ndQuadrant-provided .deb and .rpm packages. + + + + + + + monitoring and status checks: + New commands and + providing information + about a node's status and replication-related monitoring + output. + + + + + + + node rejoin: + New commands enables a failed + primary to be rejoined to a replication cluster, optionally using + pg_rewind to synchronise its data, + (note that pg_rewind may not be useable + in some circumstances). + + + + + + + automatic failover: + improved detection of node status; promotion decision based on a consensual + model, with the promoted primary explicitly informing other standbys to + follow it. The repmgrd daemon will continue + functioning even if the monitored PostgreSQL instance is down, and resume + monitoring if it reappears. Additionally, if the instance's role has changed + (typically from a primary to a standby, e.g. following reintegration of a + failed primary using ) repmgrd + will automatically resume monitoring it as a standby. + + + + + + + + new documentation: + the existing documentation spread over multiple text files + has been consolidated into DocBook format (as used by the + main PostgreSQL project) and is now available online in + HTML format. + + + The DocBook files can easily be used to create versions + of the documentation in other formats such as PDF. + + + + + + + New command line options