MySQL 9.4

MySQL 9.4 continued MySQL’s 9.x Innovation release track after 9.3. It was a feature-delivery line, not an LTS baseline: it carried forward the compatibility, server, SQL, replication, client, and operational changes introduced across the 9.x series while adding the fixes and feature work delivered for 9.4. Teams should treat the detailed 9.4 release notes and the release notes for every intervening target version as the source of truth for behavior changes, rather than assuming compatibility from the version number alone.

MySQL 9.4 has reached end of life. Remaining on it means newly found security issues, correctness defects, performance problems, and platform or dependency incompatibilities will not receive fixes for this release line. The operational risk grows as operating systems, TLS libraries, backup tooling, connectors, monitoring agents, and managed-service integrations move forward independently. Running an end-of-life Innovation release also leaves less room to schedule and test a migration: the longer a deployment diverges from a supported target, the more accumulated configuration, schema, replication, and application compatibility differences must be validated at once.

Select a currently supported MySQL target based on the team’s upgrade policy: use a current LTS line when stability and a longer maintenance horizon are the priority, or a current Innovation line only when the organization can absorb its faster cadence. Inventory server options, authentication methods, plugins and components, storage engines, replication and high-availability topology, client and connector versions, and SQL modes. Review the target version’s upgrade prerequisites and all intervening incompatibilities, then rehearse the move on a production-sized restored backup with representative application traffic. Validate backups and recovery, replication, failover, authentication, TLS, scheduled jobs, performance baselines, and monitoring before cutover. Do not plan an in-place downgrade to an older LTS line; moving from 9.4 to such a line requires a separately tested logical migration approach.