News for hackers. Stuff that matters.
Re:Call me maybe: MongoDB (2013) by jamesaguilar on Saturday July 05, 2014 @05:28PM (#7993015)
So far as I can tell, no traditional SQL systems have been tested. I'd lay a small bet that Postgres wouldn't lose data, although I don't even know if it has any kind of masterpool capability.
Re:Call me maybe: MongoDB (2013) by StavrosK on Saturday July 05, 2014 @05:33PM (#7993034)
Nah, he already tested Postgres: http://aphyr.com/posts/282-call-me-maybe-postgres
Re:Call me maybe: MongoDB (2013) by twic on Saturday July 05, 2014 @06:45PM (#7993211)
It's not a very thorough test compared to many of the others. I would guess because PostgreSQL doesn't support multi-master clustering.

However, in the test that was done, PostgreSQL did not lose data. The failure mode was that transactions were committed without the client being notified. Kind of the opposite of data loss - there is data in the database that the client doesn't know about.

Re:Call me maybe: MongoDB (2013) by Rapzid on Sunday July 06, 2014 @12:59AM (#7993822)
I believe you can use prepared transactios and some client smarts to mitigate this depending on your use case . There is some back and forth for sure, and the risk of locking the database is higher.