-
Notifications
You must be signed in to change notification settings - Fork 115
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
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
When a secondary node is dropped, the FSM is promoted from secondary to single.
#1023
opened Dec 26, 2023 by
dbamu
Upgrade to 2.1 fails: extension "pgautofailover" has no update path from version "2.0" to version "2.1"
#1018
opened Dec 6, 2023 by
Jay2k1
Switchover and failover get stuck in the report_lst status in certain configurations
#1014
opened Nov 20, 2023 by
xinferum
ERROR candidate-priority value 10 is not valid. Valid values are integers from 0 to 100 🧐
#1011
opened Oct 13, 2023 by
steinbrueckri
Previous Next
ProTip!
Updated in the last three days: updated:>2024-10-01.