Instructions for upgrading to MariaDB 10.6, noting significant changes like the default character set switch to `utf8mb3` and atomic DDL support.
For Windows, see Upgrading MariaDB on Windows.
For MariaDB Galera Cluster, see .
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.5 should be painless. However, there are some things that have changed which could affect an upgrade:
The bahaviour of sorting non-deterministic variables in a Select query can be changed , see ()
New : OFFSET. This can no longer be used as an without being quoted.
From until , tables that are of the COMPRESSED row format are read-only by default. This was intended to be the first step towards removing write support and deprecating the feature.
This plan has been scrapped, and from , COMPRESSED tables are no longer read-only by default.
From to , set the variable to OFF to make the tables writable.
From , the utf8 (and related collations) is by default an alias for utf8mb3 rather than the other way around. It can be set to imply utf8mb4 by changing the value of the system variable.
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.
See also .
This page is licensed: CC BY-SA / Gnu FDL
fsync
O_DIRECT
Empty
UTF8_IS_UTF8MB3
The variable is still present, but the *innodb and *none options have been removed as the crc32 algorithm only is supported from .
utf8
utf8mb3
utf8
utf8mb3
utf8
utf8mb3
utf8
Use instead.
Use instead.
utf8mb3