If you don't brush and floss, you're gonna get an abscess – same with MySQL updates

With less than six months to go before support for version 5.7 of relational database MySQL runs out, it appears users are ignoring recommendations to upgrade. Figures from Percona Monitoring and Management show that between 40 and 50 percent of MySQL users remain on version 5.7 despite mainstream support ending on 31 October …

[VoiceOfTruth]

Well...

-> With less than six months to go before support for version 5.7 of relational database MySQL runs out, it appears users are ignoring recommendations to upgrade.

I have a bunch of 512MB VMs on AWS. MySQL 5.7 fits in that for the low use requirements of those particular DBs. MySQL 8 very barely just fits in, which basically means it does not fit in. Just upgrade (sure, at the cost of buying larger VMs). Elsewhere MySQL runs well. But *just( telling people to upgrade is like telling somebody with weak limbs to run faster.

[Nate Amsden]

Re: Well...

512MB, wow that is tiny. I used to run utility servers (DNS/NTP/email) on 1GB 32-bit VMs in 2010 and before(maybe even 512/768MB back then I don't remember), but in 2011(at a new position) decided to standardize on 64-bit, and 1GB wasn't really enough anymore(system would start swapping), at least at some points in their life(especially doing package updates - also assuming swap was only to be used in emergency situations), so upgraded to 2GB, and more recently(Ubuntu 20.04 with default 5.4 kernel) due to kernel memory leaks had to upgrade to 3GB(or reboot more often). Not that I am low on memory have a couple TB available.

My smallest mysql db (at home) is 500MB of data and has 2GB of memory allocated to it. One of my smallest DBs at work is 1.4GB of data and has 5GB memory(started with 4, increased to 5 to get it to stop swapping).

[F. Frederick Skitty]

"Zaitsev said he was not expecting a lot of SQL users to shift from 5.7 to MariaDB instead of MySQL 8.0".

In my employer's case, we did move to MariaDB from MySQL 5.7. From a technical perspective it was an easier change than going to MySQL 8.0, and it had the added benefit of not being an Oracle product.

Now we're migrating to PostgreSQL, since it lacks the quirky behaviour of either MySQL or MariaDB and has sophisticated full text searching that means we can also dump our separate Solr setup.

[David Harper 1]

MySQL 8.0 is already rather long in the tooth, with no replacement yet announced by Oracle

What concerns me, as an open-source DBA, is that MySQL 8.0 is itself now 5 years old (it went GA in April 2018) but Oracle have not yet announced a new major version to replace it. Oracle sales people pester me and my DBA colleagues to look at their new cloud-based version of MySQL called Heatwave whenever we ask for information, and I strongly suspect that this has been Oracle's focus in their MySQL division for several years, which would explain why there's no word about MySQL 9. At this point, I'm advising users to adopt PostgreSQL rather than MySQL.