MariaDB 10.6.4 is a Stable (GA) release of MariaDB Community Server 10.6, released on 2021-08-06
Release date: 6 Aug 2021
Warning: This version can cause InnoDB file corruption on FreeBSD and on AIX. Stick to an earlier release, or upgrade to a more recent release, if you are running either of these environments. See MDEV-26537.
MariaDB 10.6 is the current stable series of MariaDB. It is an evolution of MariaDB 10.5 with several entirely new features.
MariaDB 10.6.4 is a Stable (GA) release.
Thanks, and enjoy MariaDB!
InnoDB no longer acquires advisory file locks by default ()
Encryption: Automatically disable key rotation checks for file_key_management plugin ()
Some fixes from MySQL 5.7.35 ()
Fixed scrubbing on AIX ()
A query that uses ORDER BY .. LIMIT clause and "Range checked for each record optimization" could produce incorrect results under some circumstances ()
Queries that have more than 32 equality conditions comparing columns of different tables ("tableX.colX=tableY.colY) could cause a stack overrun in the query optimizer (, )
"Condition pushdown into derived table" optimization cannot be applied if the expression being pushed refers to a derived table column which is computed from expression that has a stored function call, @session variable reference, or other similar construct. The fix for makes it so that only the problematic part of the condition is not pushed. The rest of the condition is now pushed. ()
As per the , this will be the last release of for Ubuntu 20.10 Groovy
Debian 11 Bullseye repositories added
updated to 26.4.9
Linux on IBM Z (s390x) architecture added with releases on Ubuntu-20.04 Focal
Fixes for the following :
For a complete list of changes and bugfixes made in , with links to detailed information on each push, see the .
For a full list of contributors to , see the .
buf_pool.flush_list corrupted by buffer pool resizing or ROW_FORMAT=COMPRESSED (MDEV-26200)
A query with window function on the left side of the subquery could cause a crash. (MDEV-25630)
Fixed the issue fixed in MySQL Bug #76803: DML or locking SELECT statements
that use outer joins could produce this warning in the error log: [ERROR] InnoDB: Unlock row could not find a 3 mode lock on the record. (MDEV-26106)
This page is licensed: CC BY-SA / Gnu FDL