Upgrading from MariaDB 10.11 to MariaDB 11.0
Contents
This page includes details for upgrading from MariaDB 10.11 to MariaDB 11.0. It is currently incomplete. Note that MariaDB 10.11 is maintained for five years, while MariaDB 11.0 is a short-term maintenance release, only maintained for one year.
How to Upgrade
For Windows, see Upgrading MariaDB on Windows.
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 Mariabackup.
The suggested upgrade procedure is:
- Modify the repository configuration, so the system's package manager installs MariaDB 11.0. For example,
- On Debian, Ubuntu, and other similar Linux distributions, see Updating the MariaDB APT repository to a New Major Release for more information.
- On RHEL, CentOS, Fedora, and other similar Linux distributions, see Updating the MariaDB YUM repository to a New Major Release for more information.
- On SLES, OpenSUSE, and other similar Linux distributions, see Updating the MariaDB ZYpp repository to a New Major Release for more information.
- Stop MariaDB.
- 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
- On Debian, Ubuntu, and other similar Linux distributions, execute the following:
- Install the new version of MariaDB.
- On Debian, Ubuntu, and other similar Linux distributions, see Installing MariaDB Packages with APT for more information.
- On RHEL, CentOS, Fedora, and other similar Linux distributions, see Installing MariaDB Packages with YUM for more information.
- On SLES, OpenSUSE, and other similar Linux distributions, see Installing MariaDB Packages with ZYpp for more information.
- Make any desired changes to configuration options in option files, such as
my.cnf. This includes removing any options that are no longer supported. - Start MariaDB.
- Run mariadb-upgrade.
mariadb-upgradedoes two things:- Ensures that the system tables in the mysql 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 .
Incompatible Changes Between 10.11 and 11.0
On most servers upgrading from 10.11 should be painless. However, there are some things that have changed which could affect an upgrade:
Options That Have Changed Default Values
| Option | Old default | New default |
|---|---|---|
| innodb_undo_tablespaces | 0 | 3 |
| histogram_type | DOUBLE_PREC_HB | JSON_HB |
Options That Have Been Removed or Renamed
The following options should be removed or renamed if you use them in your option files:
| Option | Reason |
|---|---|
| innodb_change_buffer_max_size | InnoDB Change Buffer removed |
| innodb_change_buffering | InnoDB Change Buffer removed |
Deprecated Options
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.
| Option | Reason |
|---|---|
| innodb_defragment | InnoDB Defragmentation is not particularly useful and causes a maintenance burden. |
| innodb_defragment_n_pages | |
| innodb_defragment_stats_accuracy | |
| innodb_defragment_fill_factor_n_recs | |
| innodb_defragment_fill_factor | |
| innodb_defragment_frequency | |
| innodb_file_per_table | |
| innodb_flush_method | |
| innodb_file_per_table | Has been set for many releases. Unsetting (the original InnoDB default) is no longer useful |
| innodb_flush_method | Mapped it to 4 new boolean parameters that can be changed while the server is running |
| log_slow_admin_statements | Use log_slow_filter without admin |
