Don’t Perform a MySQL Update After MySQL 8.0.37!

How many of you are thinking of performing a MySQL update? With the most recent news about MySQL 9 being released on July 1st, we’d guess that number is more than just a couple.

MySQL 9.0.0 is no longer available for download and that’s for a good reason – the MySQL version was removed from the downloads page because Jean-François Gagné has disclosed the bug #115517.

What’s the Bug About?

Now, the MySQL bug seems to be private, but multiple individuals and companies like Percona have already dug into the issue and have opened the MySQL update issue PS-9306 as a result. According to MySQL themselves, MySQL update 9.0.0 has a critical issue when a very large amount of tables is at play. If developers would have a very large amount of tables they’re working with, As a result of the recent MySQL update, MySQL would crash without the opportunity to be restarted. Percona says that the limit of tables for this MySQL update bug to manifest is around 10,000, while MySQL says that the limit is around 8,000.

Regardless of what’s the case, the reason why we advise you to not upgrade MySQL to any version beyond 8.0.37 before this MySQL bug is fixed would be that the affected versions seem to start from MySQL 8.0.38. Percona has determined that some of the MySQL versions affected by this MySQL update bug include MySQL 8.0.38, MySQL 8.4.1, and MySQL 9.0.0, so it’s smart to avoid upgrading altogether for now. After all, a fix should be rolled out relatively quickly.

This MySQL bug can be reproduced by running the Bash script available on Percona’s Atlassian page.

Summary

The MySQL bug #115517 is related to newer versions of MySQL and their apparent inability to support more than 10,000 tables in a single database. If this many tables are being run under the affected MySQL versions, there’s a good chance that MySQL won’t even start altogether.

For now, be on the safe side and avoid upgrading MySQL beyond 8.0.37.

Frequently Asked Questions

What is the MySQL update bug #115517?

The MySQL update bug #115517 has to do with those running bigger data sets on newer versions of MySQL. If our MySQL instance runs a lot of tables, it could crash upon restart.

Is there a fix for the MySQL update bug #115517?

To our knowledge, not so far. That’s why you should be wary when upgrading MySQL Server beyond the version 8.0.37.

Who disclosed this MySQL update bug and when?

This MySQL bug was disclosed by Jean-François Gagné in the summer of 2024.