MariaDB 10.9.2 Release Notes

The most recent release of MariaDB 10.9 is:MariaDB 10.9.8 Stable (GA) Download Now

Download 10.9.2 | Release Notes | Changelog | Overview of 10.9

Release date: 22 Aug 2022

MariaDB 10.9 is a current stable series of MariaDB, maintained until August 2023. It is an evolution of MariaDB 10.8 with several entirely new features.

MariaDB 10.9.2 is a Stable (GA) release.

For an overview of MariaDB 10.9 see theWhat is MariaDB 10.9? page.

Thanks, and enjoy MariaDB!

Notable Items

InnoDB

• InnoDB corruption due to lack of file locking ()

• with apostrophe, and mandatory words ()

• ALTER TABLE IMPORT TABLESPACE corrupts an encrypted table ()

• ALTER TABLE wrong-result fix ()

Replication

• is stored in binlog, so that CREATE TABLE on slave would always have the same effect as on master. ()

• ER_SLAVE_INCIDENT error is specified now on slave to be seen with SHOW-SLAVE-STATUS ()

• INCIDENT_EVENT is no longer binlogged when a being logged transaction can be safely rolledback ()

• sequences related row-format events are made to correspond to binlog_row_image ()

Galera

• updated to 26.4.12

• Possible to write/update with read_only=ON and not a SUPER privilege ()

• Node crashes with Transport endpoint is not connected mysqld got signal 6 ()

• Galera4 not able to report proper wsrep_incoming_addresses ()

Optimizer

• Server crash in JOIN_CACHE::free or in copy_fields ()

  • Queries that use DISTINCT and an always-constant function like COLLATION(aggegate_func(...)) could cause a server crash. Note that COLLATION() is a special function - its value is constant even if its argument is not costant.

• Crash when using ANY predicand with redundant subquery in GROUP BY clause ()

• MariaDB Server SEGV on INSERT .. SELECT ()

  • Certain queries in form "INSERT ... SELECT with_aggregate_or_window_func" could cause a crash.

• restore_prev_nj_state() doesn't update cur_sj_inner_tables correctly ()

• Wrong result with table elimination combined with not_null_range_scan ()

  • If one runs with optimizer_switch='not_null_range_scan=on' (which is not enabled by default), a query that does a join and has const tables could produce a wrong result.

• Assertion `tmp >= 0' failed in best_access_path ()

Spider

• The version number now matches the server version (and the system variable removed) ()

• and have been deprecated (, )

• Spider's high-availability feature has been deprecated ()

JSON

• : extract document fragment into JSON column ()

CONNECT

• now supports with ()

General

• now also has a session scope, not only global ()

• New option, -enable-cleartext-plugin. Option does not do anything, and is for MySQL-compatibility purposes only.

• Crash in ()

Security

• Fixes for the following :

Changelog

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

Contributors

For a full list of contributors to , see the .