3 ms·
> Lol. If that's true (and I'm not disputing it) then how would switching to MySQL fix that problem? It's explained in the blog the great-grandparent linked:
by noncoml 9y ago
> Lol. If that's true (and I'm not disputing it) then how would switching to MySQL fix that problem?
It's explained in the blog the great-grandparent linked:
https://eng.uber.com/mysql-migration/ https://eng.uber.com/mysql-migration/
- rosser 9y agoUber's explanation of the problem neglects to consider their poor usage of the tool as contributory to the problem.
- dozzie 9y agoThat's why there were so many rebuttals to their arguments.
- Thaxll 9y agoEven Postgres dev ack the problem they had, don't try to dismiss the issue it's real.
- jtc331 9y agoThere is a real issue, yes, but it’s heavily lessened by using sane scheme design, while Uber basically used the worst possible design.
- rosser 9y agoCan you point out where I dismissed anything? PostgreSQL has a write-amplification issue — especially when you index every column on a table. My point is: if you don't do that, it doesn't hurt.