Timeline for PostgreSQL : Master-Slave replication strategy and solution for 3 servers.
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 11, 2016 at 15:38 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 1, 2016 at 5:44 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 29, 2016 at 11:23 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 18, 2016 at 20:09 | answer | added | Neil McGuigan | timeline score: 1 | |
| Feb 17, 2016 at 19:56 | comment | added | We are Borg | @Neil McGuigan : yes, 9.4. | |
| Feb 17, 2016 at 19:55 | comment | added | Neil McGuigan | which version of pg? say 9.4+ :) | |
| Feb 17, 2016 at 19:53 | comment | added | We are Borg | @Neil McGuigan : i would like to write everything to x, but read from individual servers, just when any one goes down, then the master can serve the requests.. Configuration wise X is the fastest.. | |
| Feb 17, 2016 at 19:50 | comment | added | Neil McGuigan | You're asking for master-master replication actually. Which pg doesn't do natively. Can you not write everything to X and replicate to Y,Z and read from any? | |
| Feb 17, 2016 at 9:02 | history | asked | We are Borg | CC BY-SA 3.0 |