You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I am using Postgres Operator version 1.14.0 and I leave the logical backup version to default so that I won't be interfering with the default version of it later when its upgraded in future. But the problem is, the default version it takes is 1.13. If I specify the the version of logical backuip to 1.14.0 then it is working fine.
So the question is should I provide the version of logical backup
I am running it in k8s and it is only testing environment.
The text was updated successfully, but these errors were encountered:
Hi. Are you using the helm chart? There it is already fixed: #2829. The only difference between the version is the Postgres 17 support. You can always use the same tag for operator deployment and logical backup cron job. They are build with the same pipeline.
Currently I am using Postgres Operator version 1.14.0 and I leave the logical backup version to default so that I won't be interfering with the default version of it later when its upgraded in future. But the problem is, the default version it takes is 1.13. If I specify the the version of logical backuip to 1.14.0 then it is working fine.
So the question is should I provide the version of logical backup
I am running it in k8s and it is only testing environment.
The text was updated successfully, but these errors were encountered: