The most recent release of MariaDB 10.2 is:MariaDB 10.2.44 Stable (GA) Download Now
DownloadRelease NotesChangelogOverview of 10.2
Release date: 12 May 2020
MariaDB 10.2 is a previous stable series of MariaDB. It is an evolution of MariaDB 10.1 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL 5.6 and 5.7.
MariaDB 10.2.32 is a Stable (GA) release.
For an overview of MariaDB 10.2 see theWhat is MariaDB 10.2? page.
Thanks, and enjoy MariaDB!
Fixed issue that, from MariaDB 10.2.28, disabled all events created by a server with a different server_id
. Note that the fix does not re-enable affected events. (MDEV-21758)
HeidiSQL updated to 11.0 (MDEV-22032)
mariadb-backup does not honor ignore_db_dirs from server config (MDEV-19347)
mariadb-backup --ftwrl-wait-timeout
never times out on explicit lock (MDEV-20230)
FULLTEXT INDEX, Assertion ``!table->fts->in_queue' failed in
fts_optimize_remove_table` (MDEV-21550)
Wrong estimate of affected BLOB columns in update of PRIMARY KEY (MDEV-22384)
Duplicate key value is silently truncated to 64 characters in print_keydup_error
(MDEV-20604)
Session tracking returns incorrectly long tracking data (MDEV-22504)
Add pam_user_map.so
file to binary tarball package (MDEV-21913)
Running out of file descriptors and eventual crash (MDEV-18027)
mysql_upgrade is made aware of the upstream slave tables to issue warnings when that takes place (MDEV-10047)
Corruption for SET GLOBAL innodb_
string variables (MDEV-22393)
wsrep performance optimization (MDEV-7962)
mysqldump parameter, --ignore-table-data
, added (MDEV-22037)
Server can fail while replicating conditional comments (Bug#28388217)
Galera wsrep library updated to 25.3.29
Added the xml-report
option to mysql-test-run (MDEV-22176)
As per the MariaDB Deprecation Policy, this will be the last release of MariaDB 10.2 for Debian 8 "Jessie"
Fixes for the following security vulnerabilities:
Upgrading from 10.2 versions earlier than 10.2.17 is highly recommended for all Galera users due to bug MDEV-12837 which caused serious stability issues with earlier versions. See the bug issue page for more information. When upgrading from MariaDB 10.2.16 or earlier to MariaDB 10.2.17 or higher, running mysql_upgrade is required due to changes introduced in MDEV-14637.
For a complete list of changes made in MariaDB 10.2.32 with links to detailed information on each push, see the changelog.
For a full list of contributors to MariaDB 10.2.32, see the MariaDB Foundation release announcement. Thanks, and enjoy MariaDB!
This page is licensed: CC BY-SA / Gnu FDL