v1.21.1
Release date: Nov 8, 2023
Enhancements:
- Introduce support for online/hot backups with volume snapshots by using the PostgreSQL API for physical online base backups. Default configuration for hot/cold backups on a given Postgres cluster can be controlled through the
online
option and theonlineConfiguration
stanza in.spec.backup.volumeSnapshot
. Unless explicitly set, backups on volume snapshots are now taken online by default (#3102) - Introduce the possibility to override the above default settings on volume snapshot backup using the
ScheduledBackup
andBackup
resources (#3208, #3226) - Enhance cold backup on volume snapshots by reducing the time window in which the target instance (standby or primary) is fenced, by lifting it as soon as the volume snapshot have been cut and provisioned (#3210)
- During a recovery from volume snapshots, ensure that the provided volume snapshots are coherent by validating the existing labels and annotations
- The
backup
command of thecnp
plugin forkubectl
improves the volume snapshot backup experience through the--online
,--immediate-checkpoint
, and--wait-for-archive
runtime options - Enhance the
status
command of thecnp
plugin forkubectl
with progress information on active streaming base backups (#3101) - Allow the configuration of
max_prepared_statements
with the pgBouncerPooler
resource (#3174)
Fixes:
- Suspend WAL archiving during a switchover and resume it when it is completed (#3227)
- Ensure that the instance manager always uses
synchronous_commit = local
when managing the PostgreSQL cluster (#3143) - Custom certificates for streaming replication user through
.spec.certificates.replicationTLSSecret
are now working (#3209) - Set the
k8s.enterprisedb.io/cluster
label to thePooler
pods (#3153) - Reduce the number of labels in
VolumeSnapshots
resources and render them into more appropriate annotations (#3151)
Changes:
- Volume snapshot backups, introduced in 1.21.0, are now online/hot by default; in order to restore offline/cold backups set
.spec.backup.volumeSnapshot
tofalse
- Stop using the
postgresql.auto.conf
file inside PGDATA to control Postgres replication settings, and replace it with a file namedoverride.conf
(#2812)
Technical enhancements:
- Use extended query protocol for PostgreSQL in the instance manager (#3152)