For Windows, see Upgrading MariaDB on Windows instead.
For MariaDB Galera Cluster, see Upgrading from MariaDB 10.2 to MariaDB 10.3 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_upgradedoes two things:
mysqldatabase are fully compatible with the new version.
On most servers upgrading from 10.2 should be painless. However, there are some things that have changed which could affect an upgrade:
|Option||Old default value||New default value|
The following options should be removed or renamed if you use them in your option files:
|innodb_file_format||The InnoDB file format is now Barracuda, and the old Antelope file format is no longer supported.|
|innodb_file_format_check||No longer necessary as the Antelope InnoDB file format is no longer supported.|
|innodb_file_format_max||No longer necessary as the Antelope InnoDB file format is no longer supported.|
|innodb_large_prefix||Large index key prefixes were made default from MariaDB 10.2, and limiting tables to small prefixes is no longer permitted in MariaDB 10.3.|
|innodb_mtflush_threads||Replaced by the innodb_page_cleaners system variable.|
|innodb_support_xa||XA transactions are always supported.|
|innodb_use_mtflush||Replaced by the innodb_page_cleaners system variable.|
mysqldumpfrom an earlier MariaDB release cannot be used on MariaDB 10.3 and beyond.
DELETE HISTORYprivilege, running mysql_upgrade will grant
DELETE HISTORYas well.
You might consider using the following major new features in MariaDB 10.3:
© 2019 MariaDB
Licensed under the Creative Commons Attribution 3.0 Unported License and the GNU Free Documentation License.