hapostgres

ERROR candidate-priority value 10 is not valid. Valid values are integers from 0 to 100 🧐 Open

hapostgres/pg_auto_failover#1011 · 2 comments · 1 reaction · 0 assignees · Indexed Sep 17, 2026

Release 2.1 Open

release_checklist

hapostgres/pg_auto_failover#1016 · 6 comments · 0 reactions · 2 assignees · Indexed Sep 17, 2026

Citus formation upgrade path Open

hapostgres/pg_auto_failover#1021 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Error when creating Citus worker to a formation Open

hapostgres/pg_auto_failover#1022 · 2 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

When a secondary node is dropped, the FSM is promoted from secondary to single. Open

hapostgres/pg_auto_failover#1023 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Configuration parameter in pg_autoctl.cfg for the ability to clear PGDATA before running pg_basebackup Open

hapostgres/pg_auto_failover#1024 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026

How can I configure the maximum number of WAL segments a standby can lag behind the primary in pg_auto_failover? Open

hapostgres/pg_auto_failover#1027 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Question: Running with wal_level = logical? Open

hapostgres/pg_auto_failover#1030 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Monitor ERROR: invalid input syntax for type integer: "" Open

hapostgres/pg_auto_failover#1033 · 8 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

pg_autoctl --version show weird version for pg_autoctl itself Open

hapostgres/pg_auto_failover#1036 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Question) Failed to find IP Open

hapostgres/pg_auto_failover#1037 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Integration/Support of pgbackrest Open

hapostgres/pg_auto_failover#1038 · 0 comments · 2 reactions · 0 assignees · Indexed Sep 17, 2026

multiple monitoring node Open

hapostgres/pg_auto_failover#1040 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

possible values of hba_level Open

hapostgres/pg_auto_failover#1041 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Create postgresql running out of database space Open

hapostgres/pg_auto_failover#1042 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

When replacing a monitor server, candidate priority and replication quorum are reset. Open

hapostgres/pg_auto_failover#1049 · 0 comments · 2 reactions · 0 assignees · Indexed Sep 17, 2026

Pg_auto_failover with HAProxy Open

hapostgres/pg_auto_failover#1052 · 9 comments · 1 reaction · 0 assignees · Indexed Sep 17, 2026

Init monitor failed Open

hapostgres/pg_auto_failover#1053 · 4 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

The online monitor replacement is not working properly. Open

hapostgres/pg_auto_failover#1054 · 0 comments · 1 reaction · 0 assignees · Indexed Sep 17, 2026

pg_autoctl do command Issue Open

hapostgres/pg_auto_failover#1056 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

How to modify wal_keep_size Open

hapostgres/pg_auto_failover#1057 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Dropping a database Open

hapostgres/pg_auto_failover#1063 · 17 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

using pg_autoctl node_2 cannot bring back from maintenance mode Open

hapostgres/pg_auto_failover#1074 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

pg_autoctl create monitor failed on existing instance on Debian 12 Open

hapostgres/pg_auto_failover#1075 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026

HA - pg_auto_failover for two node active-passive Open

hapostgres/pg_auto_failover#1086 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

pg_autoctl create postgres Ignores --hostname, --name, --listen, and Fails to Generate pg_autoctl.conf (v2.2) Open

hapostgres/pg_auto_failover#1087 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

pg_autoctl perform failover Open

hapostgres/pg_auto_failover#1088 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

New secondary node remains in a "down" status after a switchover. This occurs when different certificate names are used on the primary and secondary nodes. Open

hapostgres/pg_auto_failover#1089 · 1 comment · 1 reaction · 0 assignees · Indexed Sep 17, 2026

How to customize the pgautofailover_replicator username and password when the second run at the first time Open

hapostgres/pg_auto_failover#1093 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Two monitors Open

hapostgres/pg_auto_failover#1095 · 0 comments · 2 reactions · 0 assignees · Indexed Sep 17, 2026

Missing https://examples.citusdata.com/mt_ref_arch/companies.csv in tutorial Open

hapostgres/pg_auto_failover#1097 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

[Enhancement] Improve configuration management to align with PostgreSQL best practices Open

hapostgres/pg_auto_failover#1102 · 2 comments · 3 reactions · 0 assignees · Indexed Sep 17, 2026

docker tutorial fails to build Open

hapostgres/pg_auto_failover#1109 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 17, 2026

pg_controldata reports number 0 on secondary and can't connect to read only session Open

hapostgres/pg_auto_failover#1112 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

NodeID conflict when changing the monitor for datanodes Open

hapostgres/pg_auto_failover#1159 · 1 comment · 1 reaction · 0 assignees · Indexed Sep 17, 2026

pgsql_retry_open_connection() leaks the PGconn from the timed-out attempt, accumulating orphaned idle backends on the monitor until max_connections is exhausted Open

hapostgres/pg_auto_failover#1178 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 17, 2026

Get new issues in your inbox