MariaDB 10.6.9 Release Notes

Download Release Notes Changelog Overview of 10.6

Release date: 15 Aug 2022

MariaDB 10.6 is the current long-term maintenance stable series of MariaDB. It is an evolution of MariaDB 10.5 with several entirely new features.

MariaDB 10.6.8 is a Stable (GA) release.

Thanks, and enjoy MariaDB!

Regressions

Unfortunately, some bugs have been found post release, so this is updated to help avoid these issues if possible. All are fixed in .

• — a crash shortly after a page merge (can be triggered by an UPDATE or DELETE or, say, rollback of an INSERT) can cause data corruption

• — if InnoDB table had a fulltext index and only one new row was inserted between the last sync (performed asynchronously by a dedicated thread) and server shutdown, the fulltext index wasn't properly updated and became out of sync with the data. Before 10.6.9 this happened silently, in 10.6.9 an assertion crashed the server after detecting the inconsistency.

• InnoDB Race condition between backups and crash recovery. last good version . Avoid by performing backups after crash recovery

Notable Items

InnoDB

• InnoDB corruption due to lack of file locking ()

• FULLTEXT search 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 ()

  • Subquery semi-join optimization could miss LooseScan or FirstMatch strategies for certain queries.

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

OpenSSL

• Backport OpenSSL-3.0 compatibility to 10.6 branch ()

JSON

• : extract document fragment into JSON column ()

CONNECT

• now supports with ()

mariadb Client

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

General

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

• Crash in ()

• ALTER TABLE ALGORITHM=NOCOPY does not work after upgrade ()

• Server crash upon CREATE VIEW with unknown column in ON condition ()

Security

• Fixes for the following :

Changelog

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

Contributors

For a full list of contributors to , see the .