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
Alternate download from mariadb.org
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 release.
For an overview of MariaDB Server 10.3 see the page.
Thanks, and enjoy MariaDB!
: Debug-only option for dumping the contents of the InnoDB change buffer to the server error log at startup.
mariadb-backup:
: mbstream recreates xtrabackup_info on same directory as backup file
: mariadb-backup creates binlog files in server binlog directory on --prepare --export step
When upgrading from or earlier to or higher, running is required due to changes introduced in.
For a complete list of changes made in , with links to detailed information on each push, see the .
For a full list of contributors to , see the .
Read-only replicas
Issues related to read only replicas are fixed:
, , , and of temporary tables are not logged to binary log, even in or mode. With earlier MariaDB versions, one can avoid the problem with temporary tables by using 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 , and 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
: 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 :
This page is licensed: CC BY-SA / Gnu FDL