MariaDB 10.2.31 Release Notes

You are viewing an old version of this article. View the current version here.

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.2

Alternate download from mariadb.org

Release date: 28 Jan 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.31 is a Stable (GA) release.

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

Thanks, and enjoy MariaDB!

Notable Changes

General

  • MDEV-21337: fix aligned_malloc()
  • MDEV-21343: Threadpool/Unix- wait_begin() function does not wake/create threa ds, when it should

Mariabackup

  • MDEV-21255: Deadlock of parallel slave and mariabackup (with failed log copy thread)

InnoDB

  • MDEV-20950: Reduce size of record offsets
  • MDEV-19176: Reduce the memory usage during recovery
  • MDEV-21429: TRUNCATE and OPTIMIZE are being refused due to "row size too large"
  • MDEV-21500: Server hang when using simulated AIO
  • MDEV-21509: Possible hang during purge of history, or rollback
  • MDEV-21511: Wrong estimate of affected BLOB columns in update
  • MDEV-21512: InnoDB may hang due to SPATIAL INDEX
  • MDEV-21513: Avoid some crashes in ALTER TABLE...IMPORT TABLESPACE

Aria

  • MDEV-14183: aria_pack segfaults in compress_maria_file

Optimizer

  • MDEV-21318: Wrong results with window functions and implicit grouping
  • MDEV-16579: Wrong result of query using DISTINCT COUNT(*) OVER (*)

Replication

  • MDEV-18046: Crashes caused by random values to the offset option of SHOW BINLOG EVENT offset command
  • MDEV-19376: Semisync Master could crash when it executed RESET MASTER and a replica reconnects using GTID protocol

Security

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.

Changelog

For a complete list of changes made in MariaDB 10.2.31 with links to detailed information on each push, see the changelog.

Contributors

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


Be notified of new MariaDB Server, Galera Cluster and Connector 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.

Comments

Comments loading...
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.