According to Oracle’s release notes, MySQL 8.0 reaches end of life (EOL) in April 2026, with version 8.0.46. After that it will get no more security fixes, and Oracle recommends upgrading to 8.4 LTS or to an Innovation release. So January’s 8.0.45 is the second-to-last release – which means now is the time to plan the MySQL upgrade.
In this article we summarise which version is worth moving to, what changed in 8.4 that could break an existing application, and how to carry out the upgrade on a Linux server.
Which MySQL version should you move to?
Since 2023, Oracle has released MySQL on two tracks: the long-term support (LTS) track rarely gets new features and is supported for a long time, while the Innovation track brings new features every quarter, but each version only gets fixes until the next one is released. These versions were released on 20 January:
| Track | Latest version | Support |
|---|---|---|
| MySQL 8.0 | 8.0.45 | Until April 2026, ending with the 8.0.46 release |
| MySQL 8.4 LTS | 8.4.8 | Planned until April 2032 |
| MySQL 9.x Innovation | 9.6.0 | Only until the next Innovation release |
For a server running a production application, 8.4 LTS is the right choice: it is the direct successor of 8.0, it can be upgraded to directly from 8.0, and under Oracle’s lifecycle rules it gets five years of premier and three years of extended support. Only choose the Innovation track if you need a specific new feature and are prepared for quarterly upgrades.
If your database runs in the cloud
In Amazon RDS for MySQL, standard support for 8.0 ends on 31 July 2026. After that, instances are automatically moved to the paid RDS Extended Support if you don’t upgrade them – this buys time, but costs money. With other cloud providers, check their own deadlines too, because they may differ from Oracle’s.
If you use MariaDB
MariaDB is a separate project that split off from MySQL, with its own lifecycle; the end of MySQL 8.0 doesn’t affect it. Many cPanel servers run MariaDB, and so do Debian’s default packages, so as a first step, check what is actually on your machine:
mysql --version
mysql -e "SELECT VERSION();"
For a new project, it is also worth considering whether it should be MySQL at all, or rather PostgreSQL.
What changed in MySQL 8.4?
Several of the new features in 8.4 can break an existing application or operations script.
mysql_native_password is disabled by default
This is the most common surprise. The old mysql_native_password authentication is disabled by default in 8.4, so users created with it can’t log in after the upgrade. Check who is affected:
SELECT user, host, plugin FROM mysql.user
WHERE plugin = 'mysql_native_password';
The lasting solution is to switch these users to the default caching_sha2_password method:
ALTER USER 'webapp'@'localhost'
IDENTIFIED WITH caching_sha2_password BY 'new-strong-password';
PHP’s mysqlnd driver has supported this since version 7.4; with older clients and custom-built applications, though, test first. As a temporary measure, the old method can be turned back on with the line mysql_native_password=ON in the [mysqld] section, but this is only a reprieve: the method is deprecated, and it has already been removed from the 9.x Innovation track.
The default_authentication_plugin setting has been removed; authentication_policy serves this purpose instead. If the old setting is left in my.cnf, the server won’t even start.
The MASTER/SLAVE syntax has been removed
The old replication commands no longer work in 8.4. If you use replication, the scripts and the monitoring have to be rewritten too:
| Old (deprecated in 8.0) | New (8.4) |
|---|---|
SHOW SLAVE STATUS |
SHOW REPLICA STATUS |
START SLAVE / STOP SLAVE |
START REPLICA / STOP REPLICA |
CHANGE MASTER TO |
CHANGE REPLICATION SOURCE TO |
SHOW MASTER STATUS |
SHOW BINARY LOG STATUS |
RESET MASTER |
RESET BINARY LOGS AND GTIDS |
Other changes
- Removed settings: for example
expire_logs_days(usebinlog_expire_logs_secondsinstead) and--skip-host-cache. These have to be taken out of the configuration file. - Changed InnoDB defaults: among others
innodb_io_capacity(10000 instead of 200),innodb_log_buffer_size(64 MiB instead of 16 MiB), and on Linuxinnodb_flush_methoddefaults toO_DIRECT. Values explicitly set in your configuration stay; where they aren’t set, the server may behave differently. - Removed tools:
mysqlpump(usemysqldumpor the MySQL Shell dump utilities instead) andmysql_upgrade(the server performs the upgrade itself at start-up). - Foreign keys: by default, 8.4 doesn’t allow creating a new foreign key that refers to a non-unique or partial key. Existing ones remain, but a warning appears in the log.
Upgrade steps
1. Check with MySQL Shell
MySQL Shell’s built-in upgrade checker goes through the server and lists what would block or affect the upgrade – deprecated settings, users, table definitions:
mysqlsh -- util checkForServerUpgrade root@localhost:3306 \
--target-version=8.4.8 --config-path=/etc/mysql/my.cnf
Errors have to be fixed before the upgrade, and warnings are worth reviewing one by one.
2. Backup
You can’t downgrade in place from 8.4 to 8.0, so the backup here isn’t a formality. Make a logical backup, and if possible, also a snapshot of the whole data directory or of the virtual machine:
mysqldump --all-databases --single-transaction --routines --events \
--triggers > backup-8.0.sql
3. Test on a copy
Restore a copy to a test server, upgrade it to 8.4, and run the application on it. That way, authentication and SQL-level problems come to light before they affect the production system.
4. The upgrade
On Debian and Ubuntu, if you use Oracle’s official APT repository, switch to the 8.4 LTS track with the mysql-apt-config package, then install the new server:
sudo dpkg-reconfigure mysql-apt-config # choose the mysql-8.4-lts track
sudo apt update
sudo apt install mysql-server
On first start-up, the server upgrades the data dictionary and the system tables itself. Afterwards, go through the error log (/var/log/mysql/error.log), and check that every application can connect. On cPanel servers, do the upgrade in WHM’s own MySQL/MariaDB upgrade interface, not by hand.
Checklist
- Inventory: which servers run MySQL 8.0, and which applications use them.
checkForServerUpgradeon every server, and fixing the errors.- Switching
mysql_native_passwordusers over, and testing the clients. - Rewriting replication scripts and monitoring for the new syntax.
- A fresh backup, with a tested restore.
- A trial upgrade on a copy, then upgrading the production servers by April.
MySQL 8.0 isn’t the only system whose support ends this year; we wrote about the risks of unsupported software in this article, and you can find last year’s overview here. We help with upgrading and running database servers; you can read more on our Infrastructure and operations page.