3.3 KiB
Standardisation on primary
To standardise terminology, primary is used to denote the read/write
node in a streaming replication cluster. master is still accepted
as a synonym (e.g. repmgr master register).
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 a standby. This replaces the configuration file parameterupstream_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 the config file.
Changed command line options
repmgr
-
--replication-userhas been deprecated; it has been replaced by the configuration file optionreplication_user. The value (which defaults to the user in theconninfostring) will be stored in the repmgr metadata for use by standby clone/follow.. -
--recovery-min-apply-delayis 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-historyis deprecated and has been replaced by the configuration file optionmonitoring_history. This enables the setting to be changed without having to modify system service files.
Changes to repmgr commands
repmgr cluster show
This now displays the role of each node (e.g. primary, standby)
and its status in separate columns.
The --csv option now emits a third column indicating the recovery
status of the node.
Configuration file changes
Required settings
The following 4 parameters are mandatory in repmgr.conf:
node_idnode_nameconninfodata_directory
Renamed settings
Some settings have been renamed for clarity and consistency:
-
node: nownode_id -
name: nownode_name -
master_reponse_timeout: nowasync_query_timeoutto 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):loglevelhas been renamed tolog_levellogfilehas been renamed tolog_filelogfacilityhas been renamed tolog_facility
Removed settings
cluster: has been removedupstream_node: see note about--upstream-node-idabove.retry_promote_interval_secs: this is now redundant due to changes in the failover/promotion mechanism; the new equivalent isprimary_notification_timeout
Logging changes
- default value for
log_levelisINFOrather thanNOTICE. - new parameter
log_status_interval, which causesrepmgrdto 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 needs to be updated to the new name:
shared_preload_libraries = 'repmgr'