The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-12-03. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB 10.3.21 Release Notes

The most recent release of MariaDB 10.3 is:
MariaDB 10.3.39 Stable (GA) Download Now

Note that this version contains an issue that disabled all events created by a server with a different server_id. See MDEV-21758 for details.

Download Release Notes Changelog Overview of 10.3

Release date: 11 Dec 2019

MariaDB 10.3 is the previous stable series of MariaDB, and 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.21 is a Stable (GA) release.

For an overview of MariaDB Server 10.3 see the What is MariaDB 10.3? page.

Thanks, and enjoy MariaDB!

Notable Changes

General

  • MDEV-13492: SEC_E_INVALID_TOKEN when server sends large message during SSL handshake

Mariabackup

  • MDEV-18310: Aria engine: Undo phase failed from incremental backup

InnoDB

  • MDEV-20949: Stop issuing 'row size' error on DML
  • MDEV-20832: Don't print "row size too large" warnings in error log if innodb_strict_mode=OFF and log_warnings<=2
  • MDEV-21024: Remove redundant writes to the redo log
  • MDEV-21069: Crash on DROP TABLE if the data file is corrupted
  • some cleanup of AIO code, to better report errors
  • MDEV-20611: MRR scan over partitioned InnoDB table produces "Out of memory" error
  • MDEV-21088: Table cannot be loaded after instant ADD/DROP COLUMN
  • MDEV-21045: heap-use-after-poison in ADD PRIMARY KEY after instant ADD COLUMN
  • MDEV-21172: Memory leak after failed ADD PRIMARY KEY
  • MDEV-21158: trx_undo_seg_free() is never redo-logged

Optimizer

  • MDEV-21044: Wrong result when using a smaller size for sort buffer
  • MDEV-20611: MRR scan over partitioned InnoDB table produces "Out of memory" error

Replication

  • MDEV-19376: Repl_semi_sync_master::commit_trx assertion failure

Versioning

  • MDEV-18929: 2nd execution of SP does not detect ER_VERS_NOT_VERSIONED
  • MDEV-21011: Table corruption reported for versioned partitioned table after DELETE

Misc

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.21, with links to detailed information on each push, see the changelog.

Contributors

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

Be notified of new MariaDB Server releases automatically by subscribing to the MariaDB Foundation community announce 'at' lists.mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc products thanks to the Notification Services.

MariaDB may already be included in your favorite OS distribution. More information can be found on the Distributions which Include MariaDB page.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.