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

MariaDB 10.3.19 Release Notes

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

After an upgrade MariaDB Server can crash if InnoDB tables exist with a FULLTEXT INDEX and a FOREIGN KEY constraint attached to them. We got reports that the crash already will be encountered on startup, but a crash is also possible at a later stage. See MDEV-20987 for more details.

Do not download or use this release.

Download Release Notes Changelog Overview of 10.3

Release date: 5 Nov 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.19 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

  • MDEV-20864: Debug-only option innodb_change_buffer_dump for dumping the contents of the InnoDB change buffer to the server error log at startup.
  • MariaBackup:
    • MDEV-18438: mbstream recreates xtrabackup_info on same directory as backup file
    • MDEV-20703: mariabackup creates binlog files in server binlog directory on --prepare --export step
  • Read-only replicas
    • Issues related to read only replicas are fixed:
    • CREATE, DROP, ALTER, INSERT and DELETE of temporary tables are not logged to binary log, even in statement or mixed mode. With earlier MariaDB versions, one can avoid the problem with temporary tables by using binlog_format=ROW in which cases temporary tables are never logged.
    • Changes to temporary tables created during read_only will not be logged even after read_only mode is disabled (for example if the replica is promoted to a primary).
    • The Admin statements ANALYZE, OPTIMIZE and REPAIR will not be logged to the binary log under read-only.
  • FULLTEXT INDEX:
    • MDEV-19647: Server hangs after dropping full text indexes and restart
    • MDEV-19529: InnoDB hang on DROP FULLTEXT INDEX
    • MDEV-19073: FTS row mismatch after crash recovery
    • MDEV-20621: FULLTEXT INDEX activity causes InnoDB hang
  • MDEV-20927: Duplicate key with auto increment
  • ALTER TABLE:
    • MDEV-20799: DROP Virtual Column crash
    • MDEV-20852: BtrBulk is unnecessarily holding dict_index_t::lock
  • System-Versioned Tables:
    • MDEV-16210: FK constraints on versioned tables use historical rows, which may cause constraint violation
    • MDEV-20812: Unexpected ER_ROW_IS_REFERENCED_2 or server crash in row_ins_foreign_report_err upon DELETE from versioned table with FK
  • Galera wsrep library updated to 25.3.28
  • Packages for Ubuntu 19.10 Eoan have been added in this release
  • Fixes for the following security vulnerabilities:

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

Contributors

For a full list of contributors to MariaDB 10.3.19, 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.