From 7bf3c78f57c7c0668b2387d39d045d7e81ce9c13 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Thu, 19 Oct 2017 13:58:41 +0900 Subject: [PATCH] Add 4.0 release notes --- doc/appendix-faq.sgml | 4 + doc/appendix-release-notes.sgml | 228 ++++++++++++++++++++++++++++++++ doc/filelist.sgml | 1 + doc/repmgr.sgml | 3 +- doc/upgrading-from-repmgr3.md | 2 +- 5 files changed, 236 insertions(+), 2 deletions(-) create mode 100644 doc/appendix-release-notes.sgml diff --git a/doc/appendix-faq.sgml b/doc/appendix-faq.sgml index d9c04827..4a5536dc 100644 --- a/doc/appendix-faq.sgml +++ b/doc/appendix-faq.sgml @@ -1,4 +1,8 @@ + + FAQ (Frequently Asked Questions) + + FAQ (Frequently Asked Questions) diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml new file mode 100644 index 00000000..d31a33e4 --- /dev/null +++ b/doc/appendix-release-notes.sgml @@ -0,0 +1,228 @@ + + Release notes + + Release notes + + + + Changes to each &repmgr; release are documented in the release notes. + Please read the release notes for all versions between + your current version and the version you are plan to upgrade to + before performing an upgrade, as there may be version-specific upgrade steps. + + + + + See also: + + + + Release 4.0beta1 + + Thu Oct 5, 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. + + + For detailed instructions on upgrading from repmgr 3.x, see + . + + + + New command line options + + + + + --dry-run: &repmgr; will attempt to perform + the action as far as possible without making any changes to the + database + + + + + --upstream-node-id: use to specify the upstream node + the standby will connect later stream from, when cloning + and registering a standby. + + + This replaces the configuration file parameter upstream_node. + as the upstream node is set when the standby is initially cloned, but can change + over the lifetime of an installation (due to failovers, switchovers etc.) so it's + pointless/confusing keeping the original value around in repmgr.conf. + + + + + + + + Changed command line options + + repmgr + + + + --replication-user has been deprecated; it has been replaced + by the configuration file option replication_user. + The value (which defaults to the user provided in the conninfo + string) will be stored in the &repmgr; metadata for use by + and . + + + + --recovery-min-apply-delay is now a configuration file parameter + recovery_min_apply_delay, to ensure the setting does not get lost + when a standby follows a new upstream. + + + + + + + repmgrd + + + + --monitoring-history is deprecated and is replaced by the + configuration file option monitoring_history. + This enables the setting to be changed without having to modify system service + files. + + + + + + + + + Configuration file changes + + Required settings + The following 4 parameters are mandatory in repmgr.conf: + + + + node_id + + + + node_name + + + + conninfo + + + + data_directory + + + + + Renamed settings + + Some settings have been renamed for clarity and consistency: + + + + node is now node_id + + + + name is now node_name + + + + master_reponse_timeout is now + async_query_timeout (to better indicate its purpose) + + + + + + + + The following configuration file parameters have been renamed for consistency + with other parameters (and conform to the pattern used by PostgreSQL itself, + which uses the prefix log_ for logging parameters): + + + + + loglevel is now log_level + + + + logfile is now log_file + + + + logfacility is now log_facility + + + + + + Removed settings + + + + + cluster has been removed + + + upstream_node - see note about + --upstream-node-id above + + + + retry_promote_interval_secsthis is now redundant due + to changes in the failover/promotion mechanism; the new equivalent is + primary_notification_timeout + + + + + Logging changes + + + + + + default value for log_level is INFO + rather than NOTICE. + + + + + + new parameter log_status_interval, which causes + repmgrd to emit a status log + line at the specified interval + + + + + + + + + + repmgrd + + The `repmgr` shared library has been renamed from repmgr_funcs to + repmgr, meaning shared_preload_libraries + in postgresql.conf needs to be updated to the new name: + + shared_preload_libraries = 'repmgr' + + + + + + diff --git a/doc/filelist.sgml b/doc/filelist.sgml index 4f8d6eed..3f1ec405 100644 --- a/doc/filelist.sgml +++ b/doc/filelist.sgml @@ -71,6 +71,7 @@ + diff --git a/doc/repmgr.sgml b/doc/repmgr.sgml index 1c1b903d..93e4fe74 100644 --- a/doc/repmgr.sgml +++ b/doc/repmgr.sgml @@ -109,8 +109,9 @@ &repmgr-cluster-cleanup; - &appendix-faq; + &appendix-release-notes; &appendix-signatures; + &appendix-faq; ]]> diff --git a/doc/upgrading-from-repmgr3.md b/doc/upgrading-from-repmgr3.md index 9c08d622..84a18363 100644 --- a/doc/upgrading-from-repmgr3.md +++ b/doc/upgrading-from-repmgr3.md @@ -4,5 +4,5 @@ Upgrading from repmgr 3 This document has been integrated into the main repmgr documentation and is now located here: - http://repmgr.org/docs/upgrading-from-repmgr-3.html + https://repmgr.org/docs/upgrading-from-repmgr-3.html