Skip to content

4.2.3

Choose a tag to compare

View all tags
@jkatz jkatz released this 21 May 13:06
· 1895 commits to master since this release
v4.2.3
00127eb

Crunchy Data announces the release of the PostgreSQL Operator 4.2.3 on May 21, 2020.

The PostgreSQL Operator is released in conjunction with the Crunchy Container Suite.

The PostgreSQL Operator 4.2.3 release includes the following software versions upgrades:

  • The PostgreSQL containers now use versions 12.3, 11.8, 10.13, 9.6.18, and 9.5.22

PostgreSQL Operator is tested with Kubernetes 1.13 - 1.18, OpenShift 3.11+, OpenShift 4.3+, Google Kubernetes Engine (GKE), and VMware Enterprise PKS 1.3+.

Changes

  • This now includes support for using the JIT compilation feature introduced in PostgreSQL 11
  • The pgBackRest stanza creation and backup jobs are retried until successful, following the Kubernetes default number of retries (6)
  • POSIX shared memory is now used for the PostgreSQL Deployments.
  • Quote identifiers for the database name and user name in bootstrap scripts for the PostgreSQL containers
  • The pgo-rmdata Job no longer calls the rm command on any data within the PVC, but rather leaves this task to the storage provisioner

Fixes

  • Fix for cloning a PostgreSQL cluster when the pgBackRest repository is stored in S3.
  • The pgo show namespace command now properly indicates which namespaces a user is able to access.
  • Ensre rsync is intalled on the pgo-backrest-repo-sync UBI7 image.
  • Default the recovery action to "promote" when performing a "point-in-time-recovery" (PITR), which will ensure that a PITR process completes.
  • Report errors in a SQL policy at the time pgo apply is executed, which was the previous behavior. Reported by José Joye (@jose-joye).
  • Allow the standard PostgreSQL user created with the Operator to be able to create and manage objects within its own user schema. Reported by Nicolas HAHN (@hahnn).
  • Correctly set the default value for archive_timeout when new PostgreSQL clusters are initialized. Reported by Adrian (@adifri).
  • Allow the original primary to be removed with pgo scaledown after it is failed over.
  • The pgo-rmdata Job will not fail if a PostgreSQL cluster has not been properly initialized.
  • The failover ConfigMap for a PostgreSQL cluster is now removed when the cluster is deleted.
  • The custom setup example was updated to reflect the current state of bootstrapping the PostgreSQL container.
  • The replica Service is now properly managed based on the existence of replicas in a PostgreSQL cluster, i.e. if there are replicas, the Service exists, if not, it is removed.
Assets 10
Loading