-
Notifications
You must be signed in to change notification settings - Fork 120
Issues: hapostgres/pg_auto_failover
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
New primary stuck at unhealthy state after network issues between original primary and the monitor
#1062
opened Jan 23, 2025 by
rmondegar
Failover stuck in "report_lsn" and "fast_forward" states indefinitely.
#1060
opened Jan 2, 2025 by
nijesh8
When replacing a monitor server, candidate priority and replication quorum are reset.
#1049
opened Sep 23, 2024 by
dbamu
pg_autoctl --version show weird version for pg_autoctl itself
#1036
opened May 28, 2024 by
epolkerman
Hung (unclosed) old connections in idle status on the monitor from datanodes
#1028
opened Jan 19, 2024 by
xinferum
How can I configure the maximum number of WAL segments a standby can lag behind the primary in pg_auto_failover?
#1027
opened Jan 17, 2024 by
zubingo
Configuration parameter in pg_autoctl.cfg for the ability to clear PGDATA before running pg_basebackup
#1024
opened Jan 9, 2024 by
xinferum
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.