Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm wondering if it is possible to have a set of SQLdb servers to which data is written and have them replicate, avoiding conflicting information.

I imagine that a Master/Slave structure would be mandatory, I would like to know if a system where servers have no hierarchy could support replication.

Currently I'm using MySQL, but I would be happy to move to another database if needed.

Any ideas? :)

share|improve this question
Related question:… – Jonas Apr 14 '10 at 7:37
up vote 1 down vote accepted

You could have a multi-master setup / cluster.


Postgresql has similar features to Mysql but it considered more enterprise class, yet is also OSS. It is easy to get excellent support for it via #postgresql on

I'm not sure if there would be some affects on ACID though.

share|improve this answer
What would you say makes Postgres more "enterprise class"? – Warner Apr 14 '10 at 4:23
Postgres has been historically more of an enterprise class database because: Better adherence to SQL Superior ACID compliance. A richer feature set It did not install a risky storage engine by default (MyIsam) Full support for foreign keys Full transactions support Please see… & for more details – Brennan Apr 14 '10 at 7:04

Multi master setup is the only one setup whith no hierarchy to comes to my mind right know. By the way, there's the DRDB option for replicating data that might fit your needs using DRDB and Heartbeat for failover.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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