-
Notifications
You must be signed in to change notification settings - Fork 248
Issues: EnterpriseDB/repmgr
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
Repmgr cannot perform failover in a cluster that is not in a healthy state.
#855
opened Jul 25, 2024 by
kwenzh
repmgr cluster crosscheck does not work with custom PostgreSQL location
#852
opened Apr 23, 2024 by
JP95Git
repmgrd autofailover not working if PR is down with File system hang
#851
opened Apr 16, 2024 by
nikhil-postgres
master node fails to automatically rejoin the cluster after recovery from failure
#850
opened Apr 11, 2024 by
nuowei2543
Issue encountered while adding script for split-brain prevention
#846
opened Feb 21, 2024 by
seunofk
LOG: could not receive data from client: Connection reset by peer
#840
opened Jan 19, 2024 by
marcofortina
CRITICAL (node "foo" (ID: 2) is not attached to expected upstream node "bar" (ID: 1) repmgr-16
#838
opened Jan 18, 2024 by
dirtyworks
**High Priority** repmgr with multi slaves replication solution is not working in k8s environment
#836
opened Dec 14, 2023 by
Bhagi33
old primary node rejoin after failover uncompatitable with pg_rewind
#829
opened Oct 11, 2023 by
Zhaoxun
repmgr keeps losing connection with local (127.0.0.1) postgresql server after hours
#828
opened Sep 27, 2023 by
Zhaoxun
Upstream connection: CRITICAL witness is not attached to expected upstream node
#827
opened Sep 4, 2023 by
mattbunter
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.