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 Upgrading from MariaDB 10.2 to MariaDB 10.3 with Galera Cluster 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 Mariabackup.

The suggested upgrade procedure is:

  1. Modify the repository configuration, so the system's package manager installs MariaDB 10.3. For example,
  2. Stop MariaDB.
  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
  4. Install the new version of MariaDB.
  5. Make any desired changes to configuration options in option files, such as my.cnf. This includes removing any options that are no longer supported.
  6. Start MariaDB.
  7. Run mysql_upgrade.
    • mysql_upgrade does two things:
      1. Ensures that the system tables in the mysql 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

OptionOld default valueNew default value
innodb_flush_method(empty)fsync
innodb_spin_wait_delay64
performance_schema_max_stage_classes150160

Options That Have Been Removed or Renamed

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

OptionReason
innodb_file_formatThe InnoDB file format is now Barracuda, and the old Antelope file format is no longer supported.
innodb_file_format_checkNo longer necessary as the Antelope InnoDB file format is no longer supported.
innodb_file_format_maxNo longer necessary as the Antelope InnoDB file format is no longer supported.
innodb_instrument_semaphores
innodb_large_prefixLarge index key prefixes were made default from MariaDB 10.2, and limiting tables to small prefixes is no longer permitted in MariaDB 10.3.
innodb_mtflush_threadsReplaced by the innodb_page_cleaners system variable.
innodb_support_xaXA transactions are always supported.
innodb_use_fallocate
innodb_use_mtflushReplaced by the innodb_page_cleaners system variable.
innodb_use_trim

Reserved Words

SQL_MODE=ORACLE

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

Functions

  • As a result of implementing Table Value Constructors, the VALUES function has been renamed to VALUE().
  • Functions that used to only return 64-bit now can return 32-bit results (MDEV-12619). This could cause incompatibilities with strongly-typed clients.

mysqldump

MariaDB Backup and Percona XtraBackup

Privileges

Major New Features To Consider

You might consider using the following major new features in MariaDB 10.3:

See Also

Comments

Comments loading...