There are currently no MariaDB 10.5 releases available, and, as a development version, details on this change may change frequently.
For MariaDB Galera Cluster, see Upgrading from MariaDB 10.4 to MariaDB 10.5 with Galera Cluster instead.
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:
sudo apt-get remove mariadb-server
sudo yum remove MariaDB-server
sudo zypper remove MariaDB-server
my.cnf
. This includes removing any options that are no longer supported. mysql_upgrade
. mysql_upgrade
does two things: mysql
database are fully compatible with the new version. On most servers upgrading from 10.4 should be painless. However, there are some things that have changed which could affect an upgrade:
Option | Old default value | New default value |
---|---|---|
innodb_checksum_algorithm | crc32 | full_crc32 |
The following options should be removed or renamed if you use them in your option files:
Option | Reason |
---|---|
innodb_checksums | Deprecated and functionality replaced by innodb_checksum_algorithms in MariaDB 10.0. |
innodb_locks_unsafe_for_binlog | Deprecated in MariaDB 10.0. Use READ COMMITTED transaction isolation level instead. |
innodb_stats_sample_pages | Deprecated in MariaDB 10.0. Use innodb_stats_transient_sample_pages instead. |
innodb_rollback_segments | Deprecated and replaced by innodb_undo_logs in MariaDB 10.0. |
max_long_data_size | Deprecated and replaced by max_allowed_packet in MariaDB 5.5. |
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 |
---|---|
innodb_undo_logs |
You might consider using the following major new features in MariaDB 10.5:
© 2019 MariaDB
Licensed under the Creative Commons Attribution 3.0 Unported License and the GNU Free Documentation License.
https://mariadb.com/kb/en/upgrading-from-mariadb-104-to-mariadb-105/