News for hackers. Stuff that matters.
Re:The State of Vacuum in Postgres by noncoml on Friday January 05, 2018 @03:19PM (#16081313)
> 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/

Re:The State of Vacuum in Postgres by rosser on Friday January 05, 2018 @03:21PM (#16081330)
Uber's explanation of the problem neglects to consider their poor usage of the tool as contributory to the problem.
Re:The State of Vacuum in Postgres by dozzie on Friday January 05, 2018 @03:27PM (#16081377)
That's why there were so many rebuttals to their arguments.
Re:The State of Vacuum in Postgres by Thaxll on Friday January 05, 2018 @07:18PM (#16082938)
Even Postgres dev ack the problem they had, don't try to dismiss the issue it's real.
Re:The State of Vacuum in Postgres by rosser on Friday January 05, 2018 @08:25PM (#16083253)
Can 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.

Re:The State of Vacuum in Postgres by jtc331 on Friday January 05, 2018 @07:30PM (#16083012)
There is a real issue, yes, but it’s heavily lessened by using sane scheme design, while Uber basically used the worst possible design.