News for hackers. Stuff that matters.
Re:Why Uber Engineering Switched from Postgres to MySQL by Negitivefrags on Tuesday July 26, 2016 @09:31PM (#12169937)
None of what you said addresses the issue that I (or they) are talking about.

On Postgres an update requires a rewrite of every index of the row.

On MySQL it only requires an update of the indexes that were touched by the update.

If you have a table with 10 indexes then this means doing 10 extra writes physically to the disk.

Re:Why Uber Engineering Switched from Postgres to MySQL by dialogbox on Tuesday July 26, 2016 @11:12PM (#12170249)
As I know, not every updates rewrite indexes in PG. It has single page clean up and HOT (heap only tuple) update optimization.

Please refer to 64~ page of https://momjian.us/main/writings/pgsql/mvcc.pdf.

Re:Why Uber Engineering Switched from Postgres to MySQL by continuational on Wednesday July 27, 2016 @02:55AM (#12171015)
10 indexes on one table seems a bit much. It sounds like a table that hasn't been normalized.
Re:Why Uber Engineering Switched from Postgres to MySQL by nsxwolf on Wednesday July 27, 2016 @03:54AM (#12171216)
Though that is quite proper for a data warehouse.
Re:Why Uber Engineering Switched from Postgres to MySQL by dikei on Wednesday July 27, 2016 @02:30PM (#12175359)
A data warehouse should use much fewer transactions though.