4 ms·
I have to do the same when I teach new developers and friends about the replication problems with PG. When you say "replication problems" then you probably mea
by moe 15y ago
I have to do the same when I teach new developers and friends about the replication problems with PG.
When you say "replication problems" then you probably mean silent slave corruption?
I'm sorry but this is still a MySQL-only feature. The PostgreSQL-replication can't go out of sync, and worse, it can't even silently fail.
In this regard (and some others) PostgreSQL sadly lacks all the fun and excitement that can be had with MySQL.
- IgorPartola 15y agoCould you elaborate on this?
- moe 15y agoThe gist is that postgres replication, by design[1], can not go out of sync. This is a major difference to MySQL replication, where silent divergence between Master/Slave is a common problem. You don't notice it until you run into spurious SQL errors or perform a manual table-checksum. In a worst case you don't notice it until that day when your master fails... [1] http://awurl.com/0g7Eshe5L#first_awesome_highlight http://awurl.com/0g7Eshe5L#first_awesome_highlight