4 ms·
If for always on or High Availability setups you want two DBs running that are in constant communication, with every write being committed on both machines sync
by sudhirj 5y ago
If for always on or High Availability setups you want two DBs running that are in constant communication, with every write being committed on both machines synchronously - so if one of them goes down the other can take its place immediately with no downtime.
Postgres has no built in support yet, but tools like STOLON exist.
- deleted 5y ago[deleted]
- eloff 5y agoPostgres doesn't support synchronous replication yet? It's had it since 9.1. I think you're referring to something else.
- pezezin 5y agoPostgreSQL has master-slave replication (one read/write master, and multiple read-only standbys), the other users are talking about multi-master replication (all the databases are read/write).
- sudhirj 5y agoYup. The synchronous replication described in the docs will allow the configuration of a hot standby, but I don’t think it allows writing to the standby, which is what true master-master does.
- eloff 5y agoI'm aware. What I'm asking is why multi master is required. You can have a read only slave that is promoted to the master. It's that little bit of downtime during failover in question? Doesn't pgpool make that possible without downtime? If you use multi master and DNS failover you still have partial downtime for every session routed to the unhealthy master. That doesn't seem to solve the problem, just a little better.