Upgrading from MariaDB 10.1 to MariaDB 10.2

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. Set to 0. It can be changed dynamically with . For example:SET GLOBAL innodb_fast_shutdown=0;

• This step is not necessary when upgrading to or later. Omitting it can make the upgrade process far faster. 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 [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.1 and 10.2

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

InnoDB Instead of XtraDB

uses as the default storage engine, rather than XtraDB, used in and before. See In most cases this should have minimal effect as the latest InnoDB has incorporated most of the improvements made in earlier versions of XtraDB. Note that certain are now ignored (although they still exist so as to permit easy upgrading).

Options That Have Changed Default Values

In particular, take note of the changes to , , , and .

Options That Have Been Removed or Renamed

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

Reserved Words

New : OVER, RECURSIVE and ROWS. These can no longer be used as without being quoted.

TokuDB

has been split into a separate package, mariadb-plugin-tokudb.

Replication

from legacy MySQL servers may require setting to NONE.

SQL Mode

has been changed; in particular, NOT NULL fields with no default will no longer fall back to a dummy value for inserts which do not specify a value for that field.

Auto_increment

columns are no longer permitted in , and . They were permitted in earlier versions, but did not work correctly.

TLS

Starting with , when the user specifies the --ssl option with a , the will not by default. In order to verify the server certificate, the user must specify the --ssl-verify-server-cert option to the . For more information, see the for the client.

Major New Features To Consider

You might consider using the following major new features in :

• now supports continuous binary log backups

See Also

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