All pages
Powered by GitBook
1 of 1

Upgrading from MariaDB 10.5 to MariaDB 10.6

How to Upgrade

For Windows, see Upgrading MariaDB on Windows.

For MariaDB Galera Cluster, see Upgrading from MariaDB 10.5 to MariaDB 10.6 with Galera Cluster.

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 MariaDB 10.6. For example,

  • On Debian, Ubuntu, and other similar Linux distributions, see Updating the MariaDB APT repository to a New Major Release for more information.

  • On RHEL, CentOS, Fedora, and other similar Linux distributions, see Updating the MariaDB YUM repository to a New Major Release for more information.

  • On SLES, OpenSUSE, and other similar Linux distributions, see Updating the MariaDB ZYpp repository to a New Major Release for more information.

  1. Stop MariaDB.

  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 Installing MariaDB Packages with APT for more information.

  • On RHEL, CentOS, Fedora, and other similar Linux distributions, see Installing MariaDB Packages with YUM for more information.

  • On SLES, OpenSUSE, and other similar Linux distributions, see Installing MariaDB Packages with ZYpp for more information.

  1. Make any desired changes to configuration options in option files, such as my.cnf. This includes removing any options that are no longer supported.

  2. Start MariaDB.

  3. 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:

The bahaviour of sorting non-deterministic variables in a Select query can be changed , see (MDEV-27745)

Reserved Word

  • New reserved word: OFFSET. This can no longer be used as an identifier without being quoted.

InnoDB COMPRESSED Row Format

From MariaDB 10.6.0 until MariaDB 10.6.5, tables that are of the COMPRESSED row format are read-only by default. This was intended to be the first step towards removing write support and deprecating the feature.

This plan has been scrapped, and from MariaDB 10.6.6, COMPRESSED tables are no longer read-only by default.

From MariaDB 10.6.0 to MariaDB 10.6.5, set the innodb_read_only_compressed variable to OFF to make the tables writable.

Character Sets

From MariaDB 10.6, the utf8 character set (and related collations) is by default an alias for utf8mb3 rather than the other way around. It can be set to imply utf8mb4 by changing the value of the old_mode system variable.

Options That Have Changed Default Values

Option
Old default value
New default value

character_set_client

utf8

utf8mb3

character_set_connection

utf8

utf8mb3

character_set_results

utf8

utf8mb3

character_set_system

utf8

utf8mb3

innodb_flush_method

fsync

O_DIRECT

old_mode

Empty

UTF8_IS_UTF8MB3

Options That Have Been Removed or Renamed

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

Option
Reason

innodb_adaptive_max_sleep_delay

innodb_background_scrub_data_check_interval

innodb_background_scrub_data_compressed

innodb_background_scrub_data_interval

innodb_background_scrub_data_uncompressed

innodb_buffer_pool_instances

innodb_checksum_algorithm

The variable is still present, but the *innodb and *none options have been removed as the crc32 algorithm only is supported from MariaDB 10.6.

innodb_commit_concurrency

innodb_concurrency_tickets

innodb_file_format

innodb_large_prefix

innodb_lock_schedule_algorithm

innodb_log_checksums

innodb_log_compressed_pages

innodb_log_files_in_group

innodb_log_optimize_ddl

innodb_page_cleaners

innodb_replication_delay

innodb_scrub_log

innodb_scrub_log_speed

innodb_sync_array_size

innodb_thread_concurrency

innodb_thread_sleep_delay

innodb_undo_logs

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.

Option
Reason

wsrep_replicate_myisam

Use wsrep_mode instead.

wsrep_strict_ddl

Use wsrep_mode instead.

Major New Features To Consider

  • See also System Variables Added in MariaDB 10.6.

See Also

  • The features in MariaDB 10.6

  • Upgrading from MariaDB 10.5 to MariaDB 10.6 with Galera Cluster

  • Upgrading from MariaDB 10.4 to MariaDB 10.5

  • Upgrading from MariaDB 10.3 to MariaDB 10.4

  • Upgrading from MariaDB 10.2 to MariaDB 10.3

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