Upgrading from MariaDB 10.2 to MariaDB 10.3

You are viewing an old version of this article. View the current version here.

How to Upgrade

The suggested upgrade procedure is:

  1. For Windows, see Upgrading MariaDB on Windows instead.
  2. Shutdown MariaDB 10.2,
  3. Take a backup (this is the perfect time to take a backup of your databases)
  4. Uninstall MariaDB 10.2
  5. Install MariaDB 10.3 [2]
  6. Run mysql_upgrade
    • Ubuntu and Debian packages do this automatically when they are installed; Red Hat, CentOS, and Fedora packages do not
    • mysql_upgrade does two things:
      1. Upgrades the permission tables in the mysql database with some new fields
      2. Does a very quick check of all tables and marks them as compatible with MariaDB 10.3
    • In most cases this should be a fast operation (depending of course on the number of tables)
  7. Add new options to my.cnf to enable features
    • If you change my.cnf then you need to restart mysqld

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

Options That Have Been Removed or Renamed

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

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_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_mtflushReplaced by the innodb_page_cleaners system variable.

Reserved Words


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


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


MariaDB Backup and Percona XtraBackup

Major New Features To Consider

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

See Also


Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.