So the major issue detailed here is that postgres basically uses immutables rows which creates performance issues with writes. Just read about their new schema

So the major issue detailed here is that postgres basically uses immutables rows which creates performance issues with writes. Just read about their new schemaless db in their blog an the first paragraph contains this: "The basic entity of data is called a cell. It is immutable, and once written, it cannot be overwritten. (In special cases, we can delete old records.) A cell is referenced by a row key, column name, and ref key. A cell’s contents are updated by writing a new version with a higher ref key but same row key and column name." So, mmm..., not saying that postgres didn't pose a problem for them but I think postgres' db model fits better to their new db then mysql. They probably had to work really hard to get mysql to work like postgres. Without this issue, it looks like two things needed.to be done with postgres that would have solved their problems have indexes that point to primary id and do logical replication (which they say a plugin solved in 9.4). Is this a case of "I got burned by something so I won't use it again"