Guide for upgrading from the previous LTS version 10.11 to 11.4, highlighting major optimizer changes, replication improvements, and SSL defaults.
This page includes details for upgrading from MariaDB 10.11 to the subsequent long-term maintenance version, MariaDB 11.4.
For Windows, see Upgrading MariaDB on Windows.
For MariaDB Galera Cluster, see Upgrading from MariaDB 11.4 to MariaDB 11.4 with Galera Cluster.
Before you upgrade, it would be best to take a backup of your database. This is always a good idea to do before an upgrade. We would recommend mariadb-backup.
The suggested upgrade procedure is:
Modify the repository configuration, so the system's package manager installs . For example,
On Debian, Ubuntu, and other similar Linux distributions, see for more information.
On RHEL, CentOS, Fedora, and other similar Linux distributions, see for more information.
On SLES, OpenSUSE, and other similar Linux distributions, see for more information.
.
Uninstall the old version of MariaDB.
On Debian, Ubuntu, and other similar Linux distributions, execute the following:sudo apt-get remove mariadb-server
On RHEL, CentOS, Fedora, and other similar Linux distributions, execute the following:sudo yum remove MariaDB-server
On SLES, OpenSUSE, and other similar Linux distributions, execute the following:sudo zypper remove MariaDB-server
Install the new version of MariaDB.
On Debian, Ubuntu, and other similar Linux distributions, see for more information.
On RHEL, CentOS, Fedora, and other similar Linux distributions, see for more information.
On SLES, OpenSUSE, and other similar Linux distributions, see for more information.
Make any desired changes to configuration options in , such as my.cnf. This includes removing any options that are no longer supported.
.
Run .
mariadb-upgrade does two things:
Ensures that the system tables in the database are fully compatible with the new version.
Does a very quick check of all tables and marks them as compatible with the new version of MariaDB .
On most servers upgrading from 10.11 should be painless. However, there are some things that have changed which could affect an upgrade:
The following options should be removed or renamed if you use them in your :
The following options should be removed or renamed if you use them in your :
The following options have been deprecated. They have not yet been removed, but will be in a future version, and should ideally no longer be used.
This page is licensed: CC BY-SA / Gnu FDL
in this manner no longer supported.
Unused code.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
Defragmenting InnoDB Tablespaces in this manner no longer supported.
See optimizer-switch.
300
1000
Superceded by alter_algorithm.
The motivation for introducing this in MySQL seems to have been to avoid stalls due to freeing undo log pages or truncating undo log tablespaces. In MariaDB, innodb_undo_log_truncate=ON should be a much lighter operation because it will not involve any log checkpoint, hence this is deprecated and ignored
Replaced with transaction_isolation to align the option and system variable.
Replaced with transaction_read_only to align the option and system variable.