Upgrading from MariaDB 10.0 to MariaDB 10.1

What You Need to Know

There are no changes in table or index formats between and , so on most servers the upgrade should be painless.

How to Upgrade

For Windows, see 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 .

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;

2. .

3. 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.0 and 10.1

As mentioned previously, on most servers upgrading from 10.0 should be painless. However, there are some things that have changed which could affect an upgrade:

Storage Engines

• The storage engine is no longer enabled by default, and the plugin needs to be specifically enabled.

• The storage engine is no longer enabled by default, and the plugin needs to be specifically enabled.

Replication

• introduces new, standards-compliant behavior for dealing with . In certain edge cases this could cause replication issues when replicating from a master to a slave using . See .

Options That Have Changed Default Values

Most of the following options have increased in value to give better performance.

Options That Have Been Removed or Renamed

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

Other Issues

Note that explicit or implicit casts from MAX(string) to INT, DOUBLE or DECIMAL now produce warnings ().

Major New Features To Consider

You might consider using the following major new features in :

• is now included by default.

Notes

See Also

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