mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-24 07:36:30 +00:00
c67aa15581
There are some circumstances, e.g. during switchover operations, where repmgr may need to operate on a data directory while the server isn't running, in which case there's no way to retrieve that information.
89 lines
2.5 KiB
Markdown
89 lines
2.5 KiB
Markdown
|
|
Standardisation on `primary`
|
|
----------------------------
|
|
|
|
To standardise terminolgy, `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 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 the config file.
|
|
|
|
Changed command line options
|
|
----------------------------
|
|
|
|
### repmgr
|
|
|
|
- `--replication-user` is now passed when registering the master server (and
|
|
optionally when registering a standby), *not* during standby clone/follow.
|
|
The value (defaults to the user in the conninfo string) will be stored in
|
|
the repmgr metadata for use by standby clone/follow..
|
|
|
|
|
|
### repmgrd
|
|
|
|
- `--monitoring-history` is deprecated and has been replaced by the
|
|
configuration file option `monitoring_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
|
|
|
|
Following 4 parameters are mandatory:
|
|
|
|
- node_id
|
|
- node_name
|
|
- conninfo
|
|
- pgdata
|
|
|
|
|
|
### Renamed settings
|
|
|
|
Some settings have been renamed for clarity/consistency
|
|
node -> node_id
|
|
name -> node_name
|
|
|
|
|
|
- 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` has been renamed to `log_level`
|
|
- `logfile` has been renamed to `log_file`
|
|
- `logfacility` has been renamed to `log_facility`
|
|
|
|
### Removed settings
|
|
|
|
- `cluster` has been removed
|
|
- `upstream_node`: see note about `--upstream-node-id` above.
|
|
|
|
### Logging changes
|
|
- default value for `log_level` is `INFO` rather than `NOTICE`.
|
|
- new parameter `log_status_interval`
|
|
|