v0.13.0
New features
- Add a
stolonctl
command to force fail a keeper (#546) - Overcome PostgreSQL synchronous replication limitation that could cause lost transactions under some events (#514)
- Users can now define
archiveRecoverySettings
in the cluster spec of a standby cluster. One of the possible use cases is to feed the standby cluster only with archived logs without streaming replication. (See Upgrade Notes) (#543) - Keeper: remove trailing new lines from provided passwords (#548)
Bug Fixes
- Sort keepers addresses in
pg_hba.conf
to avoid unneeded postgres instance reloads (#558) - Set
recovery_target_action
to promote when using recovery target settings #545) - Fixed wrong listen address used in
pg_hba.conf
whenSUReplAccessStrict
mode was enabled (#520)
and many other bug fixes and documentation improvements.
Thanks to everybody who contributed to this release.
Upgrades notes.
- The clusterspec
standbySettings
option as been replaced by thestandbyConfig
option. Internally it can contain two fieldsstandbySettings
andarchiveRecoverySettings
(see the clusterspec doc with the descriptors of this new option). If you're updating a standby cluster, BEFORE starting it you should update, usingstolonctl
, the clusterspec with the newstandbyConfig
option.