EDB Postgres® AI for CloudNativePG™ Global Cluster 1.2.2 release notes v1.2.2

Released: 16 September 2026

Highlights

  • With the fix of CVE-2026-55769 in CloudNativePG 1.28.4 or later, search_path is now pinned to pg_catalog, public, pg_temp on every operator-issued connection. The PGD operator's mutation reconciler now scopes search_path to public for the duration of each PGDGroup mutation transaction, so unqualified CREATE statements in user-authored mutations continue to land in the intended schema instead of failing with a permission error.

Supported versions

  • Kubernetes: 1.34, 1.35, 1.36
  • PostgreSQL: 17, 16, 15, and 14
  • The tested PG4K version is v1.28.4
  • Update the default PGD image to PostgreSQL 17.11 and PGD 5.9.5 expanded (image postgresql-pgd:17.11-pgd595-ubi9)
  • Update the default PGD proxy image to PGD proxy 5.9.5 (image edb-pgd-proxy:5.9.5-ubi9)

This release of EDB Postgres® AI for CloudNativePG™ Global Cluster includes the following:

Features

Description
The operator log level can now be set from the operator's ConfigMap or Secret with the OPERATOR_LOG_LEVEL key, which overrides the log level configured in the operator deployment. Accepted values are trace, debug, info, warn, and error.
The physical join job now retries transient failures on its own, with a BackoffLimit of 3, and is reported as Failed only once those retries are exhausted. See Physical join for what to do with a job that has failed.
The labels and annotations of a PGDGroup are now inherited by the physical join job it creates, so the job is selected by the same label-based tooling — network policies, cost allocation, monitoring — as the rest of the group.

Security Fixes

Description
Bump the go version to v1.27.1.
Bump grpc go module version to v1.83.2.

Bug Fixes

Description
The manager group subcommands — barman restore, join, remote join and group bootstrap — now emit logs and honor --log-level and --log-destination.