MariaDB 10.2.44 Release Notes
Release date: 20 May 2022
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.
Thanks, and enjoy MariaDB!
- Automatically generated Gtid_log_list_event is made to recognize within replication event group as a formal member (MDEV-28550)
- Replication unsafe INSERT .. ON DUPLICATE KEY UPDATE using two or more unique key values at a time with MIXED format binlogging is corrected (MDEV-28310)
- Replication unsafe INSERT .. ON DUPLICATE KEY UPDATE stops issuing unnecessary "Unsafe statement" with MIXED binlog format (MDEV-21810)
- Incomplete replication event groups are detected to error out by the slave IO thread (MDEV-27697)
- mysqlbinlog --stop-never --raw now flushes the result file to disk after each processed event so the file can be listed with the actual bytes (MDEV-14608)
- Incorrect binlogs after Galera SST using rsync and mariabackup (MDEV-27524)
- mariabackup does not detect multi-source replication slave (MDEV-21037)
- Useless warning "InnoDB: Allocated tablespace ID <id> for <tablename>, old maximum was 0" during backup stage (MDEV-27343)
- mariabackup prepare fails for incrementals if a new schema is created after full backup is taken (MDEV-28446)
- Subquery in an UPDATE query uses full scan instead of range (MDEV-22377)
- Assertion `item1->type() == Item::FIELD_ITEM ... (MDEV-19398)
- Server crashes in Expression_cache_tracker::fetch_current_stats (MDEV-28268)
- MariaDB server crash at Item_subselect::init_expr_cache_tracker (MDEV-26164, MDEV-26047)
- Crash with union of my_decimal type in ORDER BY clause (MDEV-25994)
- SIGSEGV in st_join_table::cleanup (MDEV-24560)
- Assertion `!eliminated' failed in Item_subselect::exec (MDEV-28437)
- 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.
Be notified of new MariaDB Server releases automatically by subscribing to the MariaDB Foundation community announce 'at' mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB Corporation customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB Corporation 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.