Why Oracle’s MySQL 9.0 Sparks Concern: Bugs, Innovation Gaps, and HeatWave Focus

21CTO editorial: analysts say Oracle’s focus lies elsewhere, and claiming that all innovation can run in the community edition is unfair.

Recent comments from analysts and developers express disappointment with the latest MySQL releases, fearing that Oracle’s priorities may sideline the open‑source database.

Earlier this month Oracle, traditionally a promoter of its proprietary database systems, launched MySQL 9.0 as an “innovation version.” MySQL 9.0 is now one of three Oracle‑supported iterations, alongside 8.0 (8.0.38) and the first update of 8.4 LTS (8.4.1).

MySQL error warning

Open‑source database consultancy Percona recently warned users not to upgrade beyond MySQL 8.0.37 due to a suspected severe bug. Aiven’s software engineer Jean‑François Gagné also reported an issue causing cascading failures, and Percona HA practice manager Marco Tusa opened issue PS‑9306 to investigate.

“In short, if you create a large number of tables—say 10,000—the MySQL daemon crashes on restart,” he explained.

The vulnerability is currently confidential, and Oracle has been asked to provide a fix promptly.

MySQL was originally developed by David Axmark and Michael Widenius in 1995. The Swedish company MySQL AB was acquired by Sun Microsystems in 2008, which itself was bought by Oracle in 2009. After the acquisition, Michael “Monty” Widenius forked MySQL to create MariaDB, hiring many former MySQL developers; MariaDB continues to release its own MySQL‑compatible versions, especially as a DBaaS offering.

In June, Peter Zaitsev, co‑founder of Percona and former MySQL engineer, voiced concerns that MySQL’s feature set is lagging because Oracle is concentrating on HeatWave, a proprietary analytics database built on MySQL.

Peter previously defended Oracle’s stewardship of open‑source databases, but his colleague Dave Stokes noted that MySQL 9.0 does not even match the feature richness of the earlier 8.0 release.

“MySQL 9.0 should be an ‘innovation version’ where Oracle‑provided features and improvements are accessible, and users can enjoy the latest technology,” the release claimed.

IDC research VP Carl Olofson added that while Oracle indeed focuses on HeatWave rather than MySQL, not all cutting‑edge features are suitable for the community edition.

He explained that HeatWave’s innovations—especially around vector storage and GenAI capabilities—are built on Oracle’s cloud‑based systems and cannot be realized elsewhere. Oracle treats HeatWave as a new MySQL construct, offering extra advantages via services like AutoPilot, which cannot be bundled into the MySQL project.

Olofson further noted that although Oracle offers a version on AWS, it is still operated by Oracle staff, making it unrealistic to expect all innovations to run on any hardware in the community edition.

From a technical perspective, many features are cloud‑only, raising the question of whether future MySQL or open‑source community versions will become merely thin clients.

What are your thoughts? Feel free to comment.