repmgr may do the work, but you have to script the promote.sh to migrate the hostname or elastic Ip to direct the request to the new master, after the crash you have to manually do the failback: (clone-sync-failover)
pgpool II with hot-stream mode is pretty sensitive to detect a failover and promote the slave , causing false-failover scenario.
2014-07-17 13:53 GMT-03:00 Joseph Mays <mays@xxxxxxx>:
I have a site that has a postgres database server. 24 hour availability is pretty critical to them, so I want to turn it into a redundant cluster for high availability. I currently have a streaming backup server, but we want to be able to make either server capable of accepting writes in the case one fails. The problem with streaming backup is that we can promote the backup when the master fails, but when the master comes backup you basically have to rebuild the entire database and reconfigure postgres on it to either make it the master or make it into a new streaming backup. We want something that’s much more dynamic, so writes can go either direction in the event of one or the failing, and so that things will automatically resync when a failed server in the cluster comes back online.Given these goals – pgpool-II, pgcluster, pgbouncer? Some other tool that I haven’t even considered?
Opensoft Argentina S.R.L
552 Suipacha , Piso 3to, Capital Federal
Argentina, (C1022AAR)
552 Suipacha , Piso 3to, Capital Federal
Argentina, (C1022AAR)
(*) The content of this electronic message may be privileged and confidential.
(*) If you are not an intended recipient of this email, please delete it and do not use it.
(*) The Open English name and the Open English logo are registered trademarks.
(*) Opensoft Argentina S.R.L is a vendor company of Open English LLC.
