up vote 0 down vote favorite
share [g+] share [fb]

One main issue with MySQL replication is that the slave is single threaded. This can cause replication lag.

How does Postgresql handle replication? Does it (or add-on such as slony-I) allow multi-threaded slaves?

In general, what are the pros and cons regarding MySQl & Postgresql replication? I frequently hear that MySQL replication is better than postgresql replication. Is that a fair statement? How exactly is it better?

link|improve this question
86% accept rate
till recently mysql replication was better because it was standard feature. similar question: serverfault.com/questions/11137/postgresql-replication – pQd Aug 7 '09 at 17:49
"till recently"? Did postgresql add replication as a standard feature recently? I looked at their most recent release 8.4 and I didn't see replication anywhere in there. – Continuation Aug 7 '09 at 19:04
postgresql 8.5 will have mysql-alike async. replication archives.postgresql.org/pgsql-committers/2009-12/msg00167.php – pQd Jan 10 '10 at 13:17
feedback

2 Answers

up vote 1 down vote accepted

All replication that I'm aware of for Mysql and Postgres is single threaded. Multithreading replication is a very complicated problem to solve because you have to ensure that out of order updates do not effect the final data.

link|improve this answer
feedback
up vote 0 down vote

You can get it done (at least in PostgreSQL with slony or other addons) by splitting your data up in pieces and replicate them independently. But that really only works if it's made out of independent parts that you don't need transactional integrity between, because obviously it can't maintain that if you replicate it independently.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.