3 ms·
Mysql has great replication support which everyone who does webapps requires. Postgres has bolted on solutions which all don't work well for different reasons.
by xal 17y ago
Mysql has great replication support which everyone who does webapps requires. Postgres has bolted on solutions which all don't work well for different reasons. It's really good at all the things that webapps don't tend to use when they get big though. Postgres is far the better database in terms of correctness and sometimes even in terms of speed, it's just that the web use case doesn't need real databases but replicated (fairly dumb) data stores.
- mrinterweb 17y agoI have made plenty of web applications that did not require replication. I would guess that 90%+ of web apps do not need replication due to their low profile.
- compay 17y agoMysql has great replication support which everyone who does webapps requires Not everybody who does web apps needs replication.
- monos 17y agoi'm never quite sure how important replication is for a DB to succeed. up until recently i didn't need it, and now oracle provides master/master - so that's transparent for me. and i don't have to worry about how to setup the apps to be master/slave aware. who really is using mysql replication. and how interesting was a master/slave setup - the only kind of replication provided up until 4.1 (2004). i would imagine if you know howto setup your apps to work with only one master, you would know about postgres. would really be interested if any middle-sized (not slashdot) websites use mysql replication (which setup) and since when.