Hi team,
We are planning around PostgreSQL 18 for our deployment and rely on pg_auto_failover as part of that stack.
The project documentation indicates compatibility with PostgreSQL 18, but we have not seen a git tag / source release published that clearly corresponds to PG 18 support after PostgreSQL 18 GA. That makes it harder for us to pin a supported version and validate upgrades.
There is an open pull request that appears to implement PG 18–related updates (compatibility string, Docker/Citus alignment for PG 18 builds, libnuma-dev for PG 18):
#1111
Another Issues similar #1117
Could you share:
Whether PostgreSQL 18 is officially supported today from the maintainers’ perspective (and if “docs vs. tags” are temporarily out of sync), and
When we might expect a tagged release (or another clearly communicated milestone) that includes PostgreSQL 18 support—e.g. whether that is tied to merging PR #1111, additional testing, or a planned release cycle?
Any rough guidance on timeline or release criteria would help us align our own release and testing plans.
Thank you for maintaining pg_auto_failover and for any insight you can provide.
Hi team,
We are planning around PostgreSQL 18 for our deployment and rely on pg_auto_failover as part of that stack.
The project documentation indicates compatibility with PostgreSQL 18, but we have not seen a git tag / source release published that clearly corresponds to PG 18 support after PostgreSQL 18 GA. That makes it harder for us to pin a supported version and validate upgrades.
There is an open pull request that appears to implement PG 18–related updates (compatibility string, Docker/Citus alignment for PG 18 builds, libnuma-dev for PG 18):
#1111
Another Issues similar #1117
Could you share:
Whether PostgreSQL 18 is officially supported today from the maintainers’ perspective (and if “docs vs. tags” are temporarily out of sync), and
When we might expect a tagged release (or another clearly communicated milestone) that includes PostgreSQL 18 support—e.g. whether that is tied to merging PR #1111, additional testing, or a planned release cycle?
Any rough guidance on timeline or release criteria would help us align our own release and testing plans.
Thank you for maintaining pg_auto_failover and for any insight you can provide.