Download Release Notes Changelog Overview of 10.3

Release date: 15 Aug 2018

MariaDB 10.3 is an evolution of MariaDB 10.2 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL.

MariaDB 10.3.9 is a Stable (GA) release.

For an overview of MariaDB Server 10.3 see the What is MariaDB 10.3? page or watch the webinar recording, What's new in MariaDB TX 3.0.

Thanks, and enjoy MariaDB!

Notable Changes

Notable changes of this release include:

New variable innodb_log_optimize_ddl for avoiding delay due to page flushing and allowing concurrent backup.

New variable, core_file for specifying whether to write a core file on crash.

InnoDB updated to 5.7.23

ALTER TABLE fixes: MDEV-14637 - Fix hang due to DDL with FOREIGN KEY or persistent statistics MDEV-15953 - Alter InnoDB Partitioned Table Moves Files (which were originally not in the datadir) to the datadir MDEV-16515 - InnoDB: Failing assertion: ++retries < 10000 in file dict0dict.cc line 2737 MDEV-16809 - Allow full redo logging for ALTER TABLE MDEV-16131 - Assertion `is_instant() || id == DICT_INDEXES_ID' failed in dict_index_t::instant_field_value MDEV-16830 - ALTER TABLE DROP FOREIGN KEY - unexpected end of stream error

Temporary tables: MDEV-16713 - InnoDB hang with repeating log entry

MDEV-16596 - Windows - redo log does not work on native 4K sector disks

indexed virtual columns: MDEV-15855 - Deadlock between purge thread and DDL statement

locking: MDEV-16664 - Change the default to innodb_lock_schedule_algorithm=fcfs

Galera: MDEV-15822 - WSREP: BF lock wait long for trx

MDEV-16675 - Unnecessary explicit lock acquisition during UPDATE or DELETE

Packages and a repository for openSUSE 15 have been added with this release, visit the Repository Configuration Tool for instructions on adding the repository

Fixes for the following security vulnerabilities: CVE-2018-3060 CVE-2018-3064 CVE-2018-3063 CVE-2018-3058 CVE-2018-3066



When upgrading from MariaDB 10.3.8 or earlier to MariaDB 10.3.9 or higher,

running mysql_upgrade is required due to changes introduced in MDEV-14637.

Changelog

For a complete list of changes made in MariaDB 10.3.9, with links to detailed information on each push, see the changelog.

Contributors

For a full list of contributors to MariaDB 10.3.9, see the MariaDB Foundation release announcement.