PGO upgrade caused PG13 backups to fail

[mzwettler2]

I upgraded PGO 5.3.0 to 5.5.0.

I added PG13 to PGO's values.yaml as I still have some PG13 instances (and PG13 is still officially supported):

...
  postgres_13:
    image: <<path to our internal image registry>>/crunchy-postgres:ubi8-13.9-2
...

pgBackRest was implicitly upgraded from image "crunchy-pgbackrest:ubi8-2.41-2" to image "crunchy-pgbackrest:ubi8-2.47-2".
Backups terminated with the following error:

ERROR: [103]: unable to find a valid repository:
       repo1: [ProtocolError] expected value '2.41' for greeting key 'version' but got '2.47'
       HINT: is the same version of pgBackRest installed on the local and remote host?

I had to explicitly fallback to pgBackRest image "crunchy-pgbackrest:ubi8-2.41-2" again.
Question: Is this a bug or how did you plan that we deal with such situations?

[mzwettler2]

I am a little bit confused.

I found this note:

PostgreSQL versions 16.1, 15.5, 14.10, 13.13, 12.17, and 11.22 are now available.

https://access.crunchydata.com/documentation/postgres-operator/latest/releases/5.5.x

PG13 is not mentioned within PGO 5.5.0 values.yaml nor can I find a PG 13.13 image?
What is going on here?

[andrewlecuyer]

Hi @mzwettler2, sorry for the confusion!

Please see the Supported Platforms page, which provides additional details about both PostgreSQL and Crunchy Postgres for Kubernetes availability.

https://access.crunchydata.com/documentation/postgres-operator/latest/overview/supported-platforms

Hope this helps!

[mzwettler2]

@andrewlecuyer

Only latest two Postgres releases are available through Developer program

That means, only PG15 + PG16 container images are provided as of now?

I cannot upgrade from PG13 to a newer version so quickly. But i could continue to use my currently used PG 13.9 container images with PGO 5.5.0 if i explicitly reference them ("image" key). what would be the risk of doing so?