Alexander Kukushkin

Maybe you are right. It was just easier to implement back than. If you want to change it - please open a PR.

Neither Spilo nor Patroni doing such permissions update. Please look the problem in your infrastructure.

There was already an attempt to fix it on Spilo start: https://github.com/zalando/spilo/pull/447/files We can't do anything else. Especially when the container isn't running as the root user.

The whole point of creating backups of configuration files is that configs are not actually backed up by some backup tools (for example wal-e). After restoring such a backup we...

Like it is proposed in the #422, we can introduce a new tag with the name for example `cascading`, which will show that this specific node is supposed to be...

> So it will be nice to have mechanism which will allow us to select replication source with internal knowledge in mind. Well, the thing is, that the current mechanism...

`1>2>3>4` is already quite a long chain, but you are right, there is no readiness check in the code which selects the node to replicate from. Therefore until 2 is...

Hi @joshuaboniface, Indeed, the feature is interesting, but agent-check makes a TCP connection to the configured port and only reads data from there without sending anything. Hence, it is not...

@cboltz Patroni is an open-source project and we accept any kind of contributions including documentation improvement. Please feel free to fork, update, and open a pull request.

> postgresql: connect_address: 127.0.0.1:5432 Please read the documentation: https://patroni.readthedocs.io/en/latest/SETTINGS.html#postgresql > connect_address: IP address + port through which Postgres is **accessible from other nodes and applications**. The localhost is clearly not...