Dimitri Fontaine

Hi @jchampio ; thanks for your analysis and repro steps! Could you also work on a PR to fix it? Note that I will be away in vacations next week,...

I'm not sure how we would go with the backward-compability, it seems to me that we would have a `AutoFailoverNode *pgAutoFailoverNode` partially filled, and at the moment the code doesn't...

Hi @soumyadeep2007 ; thanks for this new version of the PR. There's still more work to do. Let's also try to review the high level approach here: > * `keeper_ensure_configuration`...

Hi @Navid2zp, Thanks for keeping this cluster around and helping us debug the situation here. What I can see in the [Postgres source code for this error message](https://github.com/postgres/postgres/blob/master/src/backend/access/transam/xlog.c#L6843) and your...

I have a WIP branch that adds support for WAL-G to pg_auto_failover and that includes pushing and fetching base backups stored on a Cloud somewhere, and also proper integration of...

Hi @pashagolub ; thanks for this work! Windows compatibility is not a priority for the project at the moment, though it's still a very nice property to have. I'm leaving...

Did you close the issue because it's no longer a problem, or because it's a “wont fix” situation?

Hi @SLoeuillet. Please refresh https://pg-auto-failover.readthedocs.io/en/master/install.html#ubuntu-or-debian and use the Postgres community packaging available at apt.postgresql.org. Thanks!

See also #223 ; where my last question remains. I can't see how to fix getopt_long parsing with POSIXLY_CORRECT in a way that works both on GNU libc, macos libc,...

Note to myself: I could reproduce the problem from source with the following variation on the provided Dockerfile (thanks @asafza ), and failed to fix it when commenting out the...