Upgrading from MariaDB 10.2 to MariaDB 10.3

How to Upgrade

For Windows, see Upgrading MariaDB on Windows instead.

For MariaDB Galera Cluster, see instead.

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. . The server should be cleanly shut down, with no incomplete transactions remaining. must be set to 0 or 1 and must be less than 3.

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 [mysq](../../../../reference/sql-statements-and-structure/sql-statements/administrative-sql-statements/system-tables/the-mysql-database-tables/README.md) l 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.2 and 10.3

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

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 :

Reserved Words

• New : EXCEPT and INTERSECT. These can no longer be used as without being quoted.

SQL_MODE=ORACLE

• has introduced major new Oracle compatibility features. If you upgrade and are using this setting, please check the .

Functions

• As a result of implementing Table Value Constructors, the has been renamed to VALUE().

• Functions that used to only return 64-bit now can return 32-bit results (). This could cause incompatibilities with strongly-typed clients.

mysqldump

• in includes logic to cater for the . mysqldump from an earlier MariaDB release cannot be used on and beyond.

MariaDB Backup and Percona XtraBackup

• is not compatible with . Installations currently using XtraBackup should upgrade to before upgrading to .

Privileges

• If a user has the but not the DELETE HISTORY privilege, running will grant DELETE HISTORY as well.

Major New Features To Consider

You might consider using the following major new features in :

• See also .

See Also

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