Timeline for Postgresql Replication - Pacemaker vs DRBD
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 13, 2017 at 1:05 | answer | added | Craig Ringer | timeline score: 2 | |
| Sep 12, 2017 at 23:20 | answer | added | Matt Kereczman | timeline score: 4 | |
| Sep 12, 2017 at 20:04 | comment | added | Vérace | Have you looked at BDR? | |
| Sep 12, 2017 at 19:06 | comment | added | TheDataGuy | @RolandoMySQLDBA - Yes, I read this already, ok, lets ignore VIPs. Is this possible to setup the cluster with pacemaker+DRDB+corosync and if the master goes down the slave will act as a master and when the old master came up then it should act as a slave (without reinitiating the replication). Is this possible ? | |
| Sep 12, 2017 at 19:03 | comment | added | RolandoMySQLDBA | Although I am not a full expert with PostgreSQL, I did write up something 5.5 years ago about PostgreSQL and DRBD using, not Pacemaker, but ucarp for VIP movement : dba.stackexchange.com/questions/14201/… | |
| Sep 12, 2017 at 19:03 | comment | added | András Váczi | If you are on AWS, I'd suggest looking into Spilo | |
| Sep 12, 2017 at 18:28 | history | asked | TheDataGuy | CC BY-SA 3.0 |