major upgrade / WAL Archiving

[itmwiw]

Hello,

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.7.0
• Where do you run it - cloud or metal? Kubernetes or OpenShift? [Openshift]
• Are you running Postgres Operator in production? [no]
• Type of issue? [Bug report/question]

When trying to do an Inplace major upgrade from Postgres 12 to Postgres 13, I had an issue the upgrade. When viewing the logs, it was saying that it failed to stop the server. After some searching it was due to WAL archiving: Once I disabled the WAL archiving, the upgrade went fine. So my question is: Did I misconfigured something from my side, or is it something that can't be automatized for now (automatically disable the wal archiving, doing the upgrade and then restarting the wal archiving)? Thanks in advance

[FxKu]

Hm, no this should all be done by the inplace-upgrade.sh script. Creating a CHECKPOINT, stopping Postgres etc. Maybe you can provide some logs of Patroni (pod logs) and Postgres (although these are cycled each week).