2 ms·
In general, when a respected team sticks with a design for a long time it's safe to assume it's not a bad design but that the problem is harder than it might fi
by acdha 9y ago
In general, when a respected team sticks with a design for a long time it's safe to assume it's not a bad design but that the problem is harder than it might first appear.
In this case, I'd want to think carefully about the data volume: many places may have hundreds of transactions per second but also have queries which run for much longer periods of time and the visible state has to be accurate for all of them. That sounds a lot of contention for that shared data structure and “efficiently find all rows that aren't visible to any transaction” sounds decidedly non-trivial for busy servers with lots of data, which are generally the only ones where this matters.