The Ultimate Guide to High Availability with MariaDB

Upgrading from MariaDB 10.5 to MariaDB 10.6

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

Contents

  1. How to Upgrade
  2. Incompatible Changes Between 10.5 and 10.6
    1. Options That Have Changed Default Values
    2. Options That Have Been Removed or Renamed
    3. Deprecated Options
  3. Major New Features To Consider
  4. See Also

MariaDB 10.6 is still under active development, so details on this page will change frequently.

How to Upgrade

For Windows, see Upgrading MariaDB on Windows.

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.6. 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 mariadb-upgrade.
    • mariadb-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.5 and 10.6

On most servers upgrading from 10.5 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_methodfsyncO_DIRECT

Options That Have Been Removed or Renamed

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

OptionReason

Deprecated Options

The following options have been deprecated. They have not yet been removed, but will be in a future version, and should ideally no longer be used.

OptionReason
wsrep_strict_ddlUse wsrep_mode instead.

Major New Features To Consider

See Also

Comments

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.