4 ms·
PostgreSQL uses essentially MySQL's ROW based format (that is, it replicates the actual table changes instead of the statements). If you use purely row based re
by falcolas 14y ago
PostgreSQL uses essentially MySQL's ROW based format (that is, it replicates the actual table changes instead of the statements). If you use purely row based replication, you likely wouldn't see this in MySQL either. Of course, since TANSTAAFL, your network traffic between nodes is much higher, and the disk storage requirements grow significantly (for the binary logs).
Also, RDS doesn't offer anything but mixed format replication for slaves, and DRBD for HA.
The best middle ground when ROW based replication isn't an option is to check for inconsistencies periodically using something like pt-table-checksum, and fix them when they're found with something like pt-table-sync.
[EDIT] Can you please explain the downvotes?
- larrik 14y agoI don't know about the downvotes, but using anything non-default in MySQL is dangerous because the devs don't test well enough. I've had enough troubles just with transactions to never consider MySQL for a serious project ever again.
- falcolas 14y ago> I've had enough troubles just with transactions What kind of troubles? It's a serious question; I work with InnoDB transactions on a daily basis, and if I can find more real issues, I can usually get them resolved (or explain the behavior). MySQL is a very powerful and performant DB (and, contrary to seeming popular opinion, 100% production ready), but it's not always obvious why things work the way they do.