On the postgreSQL’s wiki, on the “Replication, Clustering, and Connection Pooling” page ( http://wiki.postgresql.org/wiki/Replication,_Clustering,_and_Connection_Pooling) , it shows the following example on replication’s requirements:
“Your users take a local copy of the database with them on laptops when they leave the office, make changes while they are away, and need to merge those with the main database when they return. Here you’d want an asynchronous, lazy replication approach, and will be forced to consider how to handle conflicts in cases where the same record has been modified both on the master server and on a local copy”
And that’s pretty much my case. But, unfortunatelly, on the same page, it says: “(…) A great source for this background is in the Postgres-R Terms and Definitions for Database Replication. The main theoretical topic it doesn’t mention is how to resolve conflict resolution in lazy replication cases like the laptop situation, which involves voting and similar schemes.”
What I want to know, is where can I find material on how to resolve this kind of situation, and wich would be the best way to do this on PostgreSQL.
Just answering my own question, if anyone ever finds it: I’m using Rubyrep http://www.rubyrep.org/ and it’s working.