Crunchy Postgres for Kubernetes 5.2.x Release Notes

Release notes for each of the 5.2.x releases.

Component versions

Crunchy Postgres
for Kubernetes
PostgrespgBackRestpgbouncerPatronipgadmin
5.2.814.112.491.213.1.24.30
5.2.714.102.471.213.1.14.30
5.2.614.92.471.193.1.14.30
5.2.514.92.471.193.1.04.30
5.2.414.82.451.192.1.74.30
5.2.314.82.451.192.1.74.30
5.2.214.72.411.182.1.74.30
5.2.114.62.401.172.1.34.30
5.2.014.52.401.172.1.34.30

Postgres extension versions

Crunchy Postgres for Kubernetes versionPostGISpgRoutingpgauditpg_cronpg_partmanpgnodemxset_userwal2jsonTimescaleDBorafcepgvector
5.2.82.5.9 (earliest)
3.3.4 (latest)
2.6.3 (earliest)
3.3.4 (latest)
1.4.3 (earliest)
1.7.0 (latest)
1.6.25.0.11.64.0.12.52.13.04.9.10.6.0
5.2.72.4.10 (earliest)
3.3.4 (latest)
2.6.3 (earliest)
3.3.4 (latest)
1.2.4 (earliest)
1.7.0 (latest)
1.6.05.0.01.64.0.12.52.12.24.7.00.5.1
5.2.62.4.10 (earliest)
3.3.4 (latest)
2.6.3 (earliest)
3.3.4 (latest)
1.2.4 (earliest)
1.7.0 (latest)
1.6.04.7.41.64.0.12.52.11.24.6.10.4.4
5.2.52.3 (earliest)
3.3.2 (latest)
2.6.3 (earliest)
3.3.1 (latest)
1.2.4 (earliest)
1.7.0 (latest)
1.5.24.7.31.44.0.12.52.10.34.2.60.4.4
5.2.42.3 (earliest)
3.3.2 (latest)
2.6.3 (earliest)
3.3.1 (latest)
1.2.4 (earliest)
1.7.0 (latest)
1.5.24.7.31.44.0.12.52.10.34.2.60.4.4
5.2.32.3 (earliest)
3.3.2 (latest)
2.6.3 (earliest)
3.3.1 (latest)
1.2.4 (earliest)
1.7.0 (latest)
1.5.24.7.31.44.0.12.52.10.34.2.6
5.2.22.3 (earliest)
3.1.8 (latest)
2.6.3 (earliest)
3.1.4 (latest)
1.2.4 (earliest)
1.6.2 (latest)
1.4.24.7.21.3.04.0.12.52.9.24.1.1
5.2.12.3 (earliest)
3.1.7 (latest)
2.6.3 (earliest)
3.1.4 (latest)
1.2.4 (earliest)
1.6.2 (latest)
1.4.24.7.11.3.03.0.02.52.8.13.25.1
5.2.02.3 (earliest)
3.1.6 (latest)
2.6.3 (earliest)
3.1.4 (latest)
1.2.4 (earliest)
1.6.2 (latest)
1.4.14.7.01.3.03.0.02.42.7.23.24.0

A bold version number indicates that the component version was updated in latest release.

5.2.8

Fixes

  • Only load datasource.pgbackrest.configuration when performing a cloud based restore.
  • Queue an event based on instance Patroni ‘master’ role change

Changes

  • PostgreSQL versions 14.11, 13.14, and 12.18 are now available.
  • pgBackRest is now at version 2.49.
  • patroni is now at version 3.1.2.
  • The orafce extension is now at version 4.9.1.
  • The pg_cron extension is now at version 1.6.2.
  • The pg_partman extension is now at version 5.0.1 for PG 16, 15 and 14.
  • The pgvector extension is now at version 0.6.0.
  • The TimescaleDB extension is now available for PG 16. The extension is at version 2.13.0 for PG 16, 15, 14, and 13.

5.2.7

Changes

  • PostgreSQL versions 14.10, 13.13, 12.17, and 11.22 are now available.
  • pgBouncer is now at version 1.21.0.
  • The orafce extension is now at version 4.7.0.
  • The pg_partman extension is now at version 5.0.0 for PG 14.
  • The pgvector extension is now at version 0.5.1.
  • The TimescaleDB extension now at version 2.12.2 for PG 14 and 13, version 2.11.2 for PG 12 and version 2.3.1 for PG 11.

5.2.6

Changes

  • Patroni is now at version 3.1.1.
  • PostGis version 3.3.4 is now available.
  • The orafce extension is now at version 4.6.1.
  • The pg_cron extension is now at version 1.6.0.
  • The pg_partman extension is now at version 4.7.4.
  • The pgAudit Analyze extension is now at version 1.0.9.
  • The pgnodemx extension is now at version 1.6.
  • The pgRouting extension is now at version 3.3.4 for PG 15 & 14.
  • pscyopg is now at version 2.9.7.
  • The TimescaleDB extension is now at version 2.11.2.

5.2.5

Changes

  • PostgreSQL versions 14.9, 13.12, 12.16, and 11.21 are now available.
  • Patroni is now at version 3.1.0.
  • pgBackrest is now at version 2.47.
  • pgBouncer is now at version 1.19.1.

Fixes

  • PostgresClusters that do not request huge pages can now be restored on nodes with huge pages.

5.2.4

Changes

  • The pgaudit_analyze tool is deprecated and may be removed in a future release.

Fixes

  • Backup jobs for S3-compatible object storage repositories would fail with a message about config hash mismatch. This is now fixed.

5.2.3

Fixes

  • PostgresClusters that do not request huge pages can now initialize on nodes with huge pages. Kubernetes container runtimes still configure cgroups incorrectly in these cases, but initdb no longer crashes.

5.2.2

This release contains new component and Postgres versions, but no additional fixes or changes.

5.2.1

Fixes

  • With the exception of the –repo option itself, PGO no longer prevents users from specifying pgBackRest options containing the string “repo” (e.g. –repo1-retention-full).
  • PGO now properly filters Jobs by namespace when reconciling restore or data migrations Job, ensuring PostgresClusters with the same name can be created within different namespaces.

5.2.0

Major Features

This and all PGO v5 releases are compatible with a brand new pgo command line interface. Please see the pgo CLI documentation for its release notes and more details.

Features

  • Added the ability to customize and influence the scheduling of pgBackRest backup Jobs using affinity and tolerations.
  • You can now pause the reconciliation and rollout of changes to a PostgreSQL cluster using the spec.paused field.
  • Leaf certificates provisioned by PGO as part of a PostgreSQL cluster's TLS infrastructure are now automatically rotated prior to expiration.
  • PGO now has support for feature gates.
  • You can now add custom sidecars to both PostgreSQL instance Pods and PgBouncer Pods using the spec.instances.containers and spec.proxy.pgBouncer.containers fields.
  • It is now possible to configure standby clusters to replicate from a remote primary using streaming replication.
  • Added the ability to provide a custom nodePort for the primary PostgreSQL, pgBouncer and pgAdmin services.
  • Added the ability to define custom labels and annotations for the primary PostgreSQL, pgBouncer and pgAdmin services.

Changes

  • All containers are now run with the minimum capabilities required by the container runtime.
  • The PGO documentation now includes instructions for rotating the root TLS certificate.
  • A fsGroupChangePolicy of OnRootMismatch is now set on all Pods.
  • The runAsNonRoot security setting is on every container rather than every pod.

Fixes

  • A better timeout has been set for the pg_ctl start and stop commands that are run during a restore.
  • A restore can now be re-attempted if PGO is unable to cleanly start or stop the database during a previous restore attempt.