Does anyone know if the performance regressions between 5.7 and 8.0 have been fixed? I no longer use MySQL regularly so I haven't been following this.
If I recall correctly, this was one of the major reasons why people were deferring this upgrade.
---
> Most notably, we encountered a problem where queries with large WHERE IN clauses would crash MySQL. We had large WHERE IN queries containing over tens of thousands of values.
The need to rewrite queries is mildly concerning. If this was part of their Rails codebase, I'm curious if these patches will make it into the ORM.
> This is the story of how we seamlessly upgraded our production fleet to MySQL 8.0.
Was it seamless? I recall GitHub being down a bunch lately, and even though the downtime is unrelated to the db upgrade, from the outside looking in, I don't know that I'd lean that hard on having done that seamlessly.
or 3) Microsoft and GitHub are huge corporations where the left hand doesn't know what the right hand is doing. Writing corporate communications is hard, but it doesn't mean we shouldn't call out mistakes when they happen.
It’s interesting that the current LTS for MySQL is already 5-years old (2018).
I’m surprised there isn’t a more current LTS.
https://en.m.wikipedia.org/wiki/MySQL
Especially when you see this quoted by MySQL team:
https://dev.mysql.com/blog-archive/introducing-mysql-innovat...