Alexander Kukushkin

@ahmetmelihbasbug, @ceremonytarkan my point about the issue template which you ignored remains.

@alexz0nder you can define the log section in the config.yaml: https://patroni.readthedocs.io/en/latest/SETTINGS.html#log

After looking at it for the second time I've got a question, why is it a prefix, and no a suffix? The suffix probably better fits into DNS? Or maybe...

Ok, it seems that the `service_prefix` is less invasive and what is more important it keeps backward compatibility.

@awiller42, sounds like a plan. Please put everything into a single PR.

Hi @Vanav, Yes, this is a problem. When both instances are on the same timeline, pg_rewind will not do anything (even on pg12): ```bash $ /usr/lib/postgresql/12/bin/pg_rewind -D data/pg12.1 -n -P...

@thedodd yes and no. This implementation is trying to make a difference between the reasons why the update of the leader lock failed and the failsafe mechanism triggers only when...

> If I then delete the K8s RoleBinding which grants Patroni access to the K8s API (for updating endpoints/services/labels &c), it looks like the primary is still demoting. Technically, the...

@alexeyklyukin yeah, nodes must be able to communicate with each other using credentials and/or client certificates. Sure, we can call the `POST /failsafe` in order to make sure that authentication...

> What is my mistake? @anyafit for existing clusters one should use `patronictl edit-config` to enable it: https://github.com/zalando/patroni/blob/e54f736651743a2521bdf393f067ea191ae08e19/docs/dcs_failsafe_mode.rst You can also check whether the feature is enabled using `patronictl show-config`.