For the complete documentation index, see llms.txt. This page is also available as Markdown.

Upgrading from MariaDB 11.8 to MariaDB 12.3

Upgrade guide for moving from MariaDB 11.8 to 12.3, covering the upgrade procedure, removed options, and replication caveats.

This page includes details for upgrading from MariaDB 11.8, the previous long-term maintenance version, to MariaDB 12.3.

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 mariadb-backup.

The suggested upgrade procedure is:

  1. Modify the repository configuration, so the system's package manager installs MariaDB 12.3.

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

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

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

  2. Uninstall the old version of MariaDB.

    1. On Debian, Ubuntu, and other similar Linux distributions, execute the following: sudo apt-get remove mariadb-server

    2. On RHEL, CentOS, Fedora, and other similar Linux distributions, execute the following: sudo yum remove MariaDB-server

    3. On SLES, OpenSUSE, and other similar Linux distributions, execute the following: sudo zypper remove MariaDB-server

  3. Install the new version of MariaDB.

    1. On Debian, Ubuntu, and other similar Linux distributions, see Installing MariaDB Packages with APT for more information.

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

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

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

  5. Run mariadb-upgrade, to:

    1. Ensure that the system tables in the mysql database are fully compatible with the new version.

    2. Perform a very quick check of all tables and marks them as compatible with the new version of MariaDB.

Incompatible Changes Between 11.8 and 12.3

On most servers upgrading from 11.8 should be painless. However, there are some things that have changed which could affect an upgrade:

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

Deprecated in MariaDB 10.5.0 and removed in MariaDB 12.0. No longer needed, as the server handles large result sets automatically.

Deprecated alias for default_storage_engine since MariaDB 5.5, and removed in MariaDB 12.0. Use default_storage_engine instead.

Read-only variable deprecated in MariaDB 10.5.3 and removed in MariaDB 12.0.

New Reserved Words

CONVERSION, ST_COLLECT, and TO_DATE are now reserved words. This only affects you if you use one of them as an unquoted identifier (for example, a table, column, or variable name) — quote it or rename it before upgrading, otherwise the statement will fail to parse. For the full list of 12.3 changes, see Features in MariaDB 12.3.

Changes in Replication Behavior

Deprecated Options

The MYSQLD_OPTS environment variable for the systemd service is deprecated. Place configuration options directly into option files, such as my.cnf, instead.

See Also

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

spinner

Last updated

Was this helpful?