Re:Thoughts on Uber’s List of Postgres Limitations
by Illniyar on Wednesday August 03, 2016 @11:06AM
(#12218452)
Well, for that matter, as I understood it, they also have no transactions nor atomicity and are basically eventually consistant , though these I'm simply inferring from their posts, it was not stated as far as I can remember.
So MVCC also has almost zero bearing on what they are doing.
Re:Thoughts on Uber’s List of Postgres Limitations
by spotman on Wednesday August 03, 2016 @12:38PM
(#12219276)
Just because you may not always use the database with the BEGIN/COMMIT semantics, that absolutely does not mean that "MVCC has almost no bearing on what they are doing".
MVCC and how it has been implemented in the two storage engines in discussion here absolutely has a lot to do with it.
Postgres is lacking in these scenarios, whereas a particular fine tuned version (or fork) of InnoDB (or MyRocks or whatever they end up chosing) handles this better.
See Facebook's "mysql-5.6" branch, that has hundreds of patches piled on to support especially these taxing workloads.