Issues
- 0
repmgr switch over fails
#718 opened - 0
- 0
When "repmgr standby switchover" is used and action commands are wrong, no details are printed
#716 opened - 0
In ubuntu 20.04 package, "repmgr standby switchover" seems to have wrong "actions" commands
#715 opened - 0
- 1
How is a promotion candidate picked?
#713 opened - 1
repmgr standby clone doesn't create all the needed directories out of the box in Ubuntu 20.04
#712 opened - 1
too many forks
#711 opened - 0
repmgr switchover fails with
#710 opened - 0
rejoin hangs
#709 opened - 4
- 2
Repmgr 5.2.1 rpm naming convention
#707 opened - 2
Postgres major upgrade with repmgr
#706 opened - 2
inaccessible via SSH
#705 opened - 0
standby is not following after registering
#704 opened - 7
switchover fails on LSN
#703 opened - 5
- 4
Question - How do I migrate a database from a standalone Postgresql server to a Repmgr cluster?
#701 opened - 2
- 2
2 standbys promoting
#699 opened - 0
- 2
- 4
- 5
Bug: reconnect_interval not working
#695 opened - 1
repmgr doesn't identify a hung child node
#694 opened - 4
- 8
- 0
Debian package for repmgr 5.2.1
#691 opened - 2
repmgr daemon status is not documented
#690 opened - 1
- 2
- 2
repmgr prevents postgresql upgrade?
#685 opened - 0
- 6
Automatic failover not working when terminating the process of postgres server on primary
#683 opened - 1
repmgr doesn't close connections when checking new primary after old primary has gone down
#682 opened - 3
- 2
- 1
- 2
- 1
repmgr 5.1 : wal replay pending on standby
#677 opened - 5
- 3
- 8
It is possible that the "reconnect_interval" parameter does not work in repmgr version 5.2.0
#673 opened - 0
- 0
replication lag with 20 minutes.
#670 opened - 1
- 4
After failed primary rejoin the new primary, the postgre service is inactive in both servers
#668 opened - 11
- 7
- 3
Can't start psql cluster after standby clone
#664 opened