Please, answer some short questions which should help us to understand your problem / question better?
Due to an issue with the my environment, it was necessary to increase the following values of loop_wait, retry_timeout, and ttl.
This was done by updating PostgreSQL configuration as follows
oc get postgresql postgres -o json | jq -r '.spec.patroni' { "loop_wait": 60, "retry_timeout": 60, "ttl": 180 }
All changes were correctly applied without any manual intervention.
Upon resolution of environmental issue, same set of values was removed from PostgreSQL configuration.
Problem is that the those values were not removed from the Patroni configuration, they remained the same. This was tested by checking patronictl show-config output and directly in postgres.yml
Expectation was that they would be assigned to their corresponding default values.
https://patroni.readthedocs.io/en/latest/dynamic_configuration.html
Is this expected behaviour or a bug?
Once, when Patroni configuration is specified within the PostgreSQL configuration, is it necessary for us to manage it manually, or can the operator ensure that the correct values are applied when such configuration is removed?
Please, answer some short questions which should help us to understand your problem / question better?
http://ghcr.io/zalando/postgres-operator:v1.13.0
OpenShift & GKE
yes
Bug
Due to an issue with the my environment, it was necessary to increase the following values of loop_wait, retry_timeout, and ttl.
This was done by updating PostgreSQL configuration as follows
oc get postgresql postgres -o json | jq -r '.spec.patroni' { "loop_wait": 60, "retry_timeout": 60, "ttl": 180 }All changes were correctly applied without any manual intervention.
Upon resolution of environmental issue, same set of values was removed from PostgreSQL configuration.
Problem is that the those values were not removed from the Patroni configuration, they remained the same. This was tested by checking
patronictl show-configoutput and directly in postgres.ymlExpectation was that they would be assigned to their corresponding default values.
https://patroni.readthedocs.io/en/latest/dynamic_configuration.html
Is this expected behaviour or a bug?
Once, when Patroni configuration is specified within the PostgreSQL configuration, is it necessary for us to manage it manually, or can the operator ensure that the correct values are applied when such configuration is removed?