Upgrading from MariaDB 10.4 to MariaDB 10.5

How to Upgrade

For Windows, see Upgrading MariaDB on Windows instead.

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:

1. 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.

1. .

2. 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

1. 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.

1. Make any desired changes to configuration options in , such as my.cnf. This includes removing any options that are no longer supported.

2. .

3. Run .

• mysql_upgrade does two things:

  1. Ensures that the system tables in the database are fully compatible with the new version.

  2. Does a very quick check of all tables and marks them as compatible with the new version of MariaDB .

Incompatible Changes Between 10.4 and 10.5

On most servers upgrading from 10.4 should be painless. However, there are some things that have changed which could affect an upgrade:

Binary name changes

All binaries previously beginning with mysql now begin with mariadb, with symlinks for the corresponding mysql command.

Usually that shouldn't cause any changed behavior, but when starting the MariaDB server via , or via the script symlink, the server process will now always be started as mariadbd, not mysqld.

So anything looking for the mysqld name in the system process list, like e.g. monitoring solutions, now needs for mariadbd instead when the server / service is not started directly, but via mysqld_safe or as a system service.

GRANT PRIVILEGE changes

A number of statements changed the privileges that they require. The old privileges were historically inappropriately chosen in the upstream. 10.5.2 fixes this problem. Note, these changes are incompatible to previous versions. A number of GRANT commands might be needed after upgrade.

• SHOW BINLOG EVENTS now requires the BINLOG MONITOR privilege (requred REPLICATION SLAVE prior to 10.5.2).

• SHOW SLAVE HOSTS now requires the REPLICATION MASTER ADMIN privilege (required REPLICATION SLAVE prior to 10.5.2).

Options That Have Changed Default Values

Options That Have Been Removed or Renamed

The following options should be removed or renamed if you use them in your :

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.

Major New Features To Consider

You might consider using the following major new features in :

• The allows one to archive MariaDB tables in Amazon S3, or any third-party public or private cloud that implements S3 API.

• columnar storage engine.

• See also .

See Also

_{This page is licensed: CC BY-SA / Gnu FDL}