An upgrading guide for unmaintained versions of MariaDB Community Server.
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:
Modify the repository configuration, so the system's package manager installs . For example,
On Debian, Ubuntu, and other similar Linux distributions, see for more information.
On RHEL, CentOS, Fedora, and other similar Linux distributions, see for more information.
On SLES, OpenSUSE, and other similar Linux distributions, see for more information.
.
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
Install the new version of MariaDB.
On Debian, Ubuntu, and other similar Linux distributions, see for more information.
On RHEL, CentOS, Fedora, and other similar Linux distributions, see for more information.
On SLES, OpenSUSE, and other similar Linux distributions, see for more information.
Make any desired changes to configuration options in , such as my.cnf. This includes removing any options that are no longer supported.
.
Run .
mariadb-upgrade does two things:
Ensures that the system tables in the database are fully compatible with the new version.
Does a very quick check of all tables and marks them as compatible with the new version of MariaDB .
On most servers upgrading from 10.7 should be painless. However, there are some things that have changed which could affect an upgrade:
The following options should be removed or renamed if you use them in your :
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.
You might consider using the following major new features in :
Stored procedures already have support for the parameter qualifiers. Added as well for and (IN only) ().
Individual columns in the can now be explicitly sorted in the ascending or descending order. This can be useful for optimizing certain cases (, , , ).
See also .
This page is licensed: CC BY-SA / Gnu FDL
134217728
Autosized
1
0
On Linux and Windows, the physical block size of the underlying storage is instead detected and used.
MariaDB now deletes orphan files, so this setting should never be necessary.