Dimitri Fontaine

Hi @s4ke ; thanks for asking. Yes that's on the roadmap, see https://github.com/citusdata/pg_auto_failover/pull/596. This is the beginning of the work, more ideas are there to explore around the concepts. Meanwhile...

Docs build preview is available at https://pg-auto-failover.readthedocs.io/en/feature-citus/intro.html#citus-architecture and https://pg-auto-failover.readthedocs.io/en/feature-citus/citus.html ; and then https://pg-auto-failover.readthedocs.io/en/feature-citus/quickstart-cluster.html etc.

> Would be good to add the coordinator to the metadata automatically. This is required for a lot of features now. That a good comment, I think we should act...

Closing the issue because I can't reproduce here. Consider using the latest release of pg_auto_failover as listed on this page: https://github.com/citusdata/pg_auto_failover/releases. For that you might want to use [apt.postgresql.org](https://apt.postgresql.org).

See #923.

By the way pg_auto_failover v2.0 has now been released with support for Postgres 15. See https://github.com/citusdata/pg_auto_failover/releases/tag/v2.0 for details.

Hi @legrandlegrand ; thanks for reporting an issue here. One thing that is strange to me is why would you first stop a node and then perform a switchover? pg_autoctl...

Hi @raivil ; I still want to add support for archiving in pg_auto_failover yes. I have no idea of when I will be able to get back on this work...

Given the following in our function pg_basebackup https://github.com/citusdata/pg_auto_failover/blob/d7997ffc3f1209483a37fe7e8ed49fe7a000f664/src/bin/pg_autoctl/pgctl.c#L1280 I would say that https://github.com/citusdata/pg_auto_failover/pull/870 indeed fixed this.

> This is getting kind of ridiculous @DimCitus ... how can anyone use `pg_auto_failover` in any production environment without this. At this point we are definitely looking at alternatives. Please...