Open lkgGitHub opened 1 year ago
same problem
Observed the exact same issue more than once on an instance, resolves if the read replica is restarted
same problem
same issue
same here
Still reproducible on latest operator v1.12.2. Any updates about this issue?
Same problem
Same problem
I have two pod in kubernetes, postgres-service-0 and postgres-service-1. First postgres-service-1 is master. After PostgreSQL master-slave failover, Application client connection PostgreSQL error:"pg: cannot set transaction read write mode during recovery". But PostgreSQL pods are all running. When I restart the application, it can be restored.
Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.8.2 spilo-14:2.1-p7
Where do you run it - cloud or metal? Kubernetes or OpenShift? Kubernetes
Are you running Postgres Operator in production? [yes | no] yes
postgres-service-1
postgres-service-0 log:
Some general remarks when posting a bug report: