Why Uber Engineering Switched from Postgres to MySQL (2016)
1–10 of 133 posts
Re: Why Uber Engineering Switched from Postgres to MySQL (2016)
#2because its simpler? i found postgres to be overly complicated compared to MySQL/Maria
Re: Why Uber Engineering Switched from Postgres to MySQL (2016)
#3because its simpler? i found postgres to be overly complicated compared to MySQL/Maria
Define: "complicated"
Re: Why Uber Engineering Switched from Postgres to MySQL (2016)
#4Re: Why Uber Engineering Switched from Postgres to MySQL (2016)
#5Previous discussions:
2016: https://news.ycombinator.com/item?id=12166585
2018: https://news.ycombinator.com/item?id=17280239
Community responses:
Re: Why Uber Engineering Switched from Postgres to MySQL (2016)
#62016
Re: Why Uber Engineering Switched from Postgres to MySQL (2016)
#7Re: Why Uber Engineering Switched from Postgres to MySQL (2016)
#8Re: Why Uber Engineering Switched from Postgres to MySQL (2016)
#9Earlier quoted context omitted.
Define: "complicated"
PostgreSQL: "your date 2020-02-31 isn't a date, fix that" MySQL: "2020-02-31? Whatever man, I'll just enter something..."
Considering the US uses a weird date format, I definitely prefer the former in combination with input sanitation forcing you to thing about your actions before assuming the database will fix it for you.
Re: Why Uber Engineering Switched from Postgres to MySQL (2016)
#10Has Postgres architecture changed since Postgres 9.2 in terms of the inefficiencies mentioned in the article?