4 ms·
Well, it really doesn't help that from the top-5 engines on his slides, only Postgres doesn't have a completely horrible performance profile for serializable tr
by marcosdumay 3y ago
Well, it really doesn't help that from the top-5 engines on his slides, only Postgres doesn't have a completely horrible performance profile for serializable transactions. So, people that try to learn about it run away quite quickly.
But I'm not sure if most systems need it anyway. Personally, I remember very few times where I had to change from the default transaction model.
As a rule, when people need full serializability, they create it with some other, more flexible mechanism.
- cmrdporcupine 3y agoPerhaps fair, but I think though this ties back to one point I was making: "And then I'd say that this general lack of enthusiasm around the relational model and ACID means that people haven't demanded the right things from their database tooling." In general there are plenty of solutions in database research and implementation. But because the broad community of developers doesn't put data first, and have a low expectation and knowledge of what a DBMS can and should do... It took us years to get to the place where Postgres is common place instead of e.g. MySQL; and back in the day "serious" folks spent tens of thousands on Oracle licenses... I guess that's progress, but there's so much more that can be done in this sphere.