v1.15.2
Release date: Jul 7, 2022 (patch release)
Enhancements:
- Improve logging of the instance manager during switchover and failover
- Require Barman >= 3.0.0 for future support of PostgreSQL 15 in backup and recovery
Changes:
- Set the default operand image to PostgreSQL 14.4
Fixes:
- Fix the initialization order inside the
WithActiveInstance
function that starts the CSV log pipe for the PostgreSQL server, ensuring proper logging in the cluster initialization phase - this is especially useful in bootstrap operations like recovery from a backup are failing (before this patch, such logs were not sent to the standard output channel and were permanently lost) - Avoid an unnecessary switchover when a hot standby sensitive parameter is decreased, and the primary has already restarted
- Properly quote role names in
ALTER ROLE
statements - Backup and recovery:
- Fix the algorithm detecting the closest Barman backup for PITR, which was comparing the requested recovery timestamp with the backup start instead of the end
- Fix Point in Time Recovery based on a transaction ID, a named restore point, or the “immediate” target by providing a new field called
backupID
in therecoveryTarget
section - Fix encryption parameters invoking
barman-cloud-wal-archive
andbarman-cloud-backup
commands - Stop ignoring
barmanObjectStore.serverName
option when recovering from a backup object store using a server name that doesn’t match the current cluster name
cnpg
plug-in:- Make sure that the plug-in complies with the
-n
parameter when specified by the user - Fix the
status
command to sort results and remove variability in the output
- Make sure that the plug-in complies with the