MariaDB 10.6.22 Release Notes
Alternate download from mariadb.org
MariaDB 10.6 is a current long-term series of MariaDB, maintained until July 2026. It is an evolution of MariaDB 10.5 with several entirely new features.
MariaDB 10.6.22 is a Stable (GA) release.
Thanks, and enjoy MariaDB!
Notable Items
Storage Engines
InnoDB
Incorrect undo logging for indexes on virtual columns whose index ID does not fit in 32 bits (MDEV-36613)
Race conditions between ALTER TABLE or OPTIMIZE TABLE and the purge of transaction history were fixed. (MDEV-36122)
ASAN errors in dict_sys_t::load_table / get_foreign_key_info after failing to load a table (MDEV-33167)
CREATE INDEX fails to heal a FOREIGN KEY constraint (MDEV-35962)
Doublewrite recovery of innodb_checksum_algorithm=full_crc32 page_compressed pages does not work (MDEV-36180)
innodb_snapshot_isolation=1 gives error for not committed row changes (MDEV-36639)
The deprecated parameter innodb_purge_rseg_truncate_frequency is not being recognized (MDEV-36378)
dict_stats_fetch_from_ps() unnecessarily holds exclusive dict_sys.latch (MDEV-35436)
Stall and crash when page cleaner fails to generate free pages during Async flush (MDEV-36226)
Performance regression in INSERT…SELECT due to unnecessarily making InnoDB log durable. (MDEV-35813)
Spider
The untested ha_spider::index_first_internal constructs broken queries (MDEV-36324)
Unexpected error 1264 'Out of Range Value for Column' when inserting into ... select ... from a spider table (MDEV-35874)
Tests calling the udf spider_copy_tables fail with --view-protocol (MDEV-36335)
Optimizer
group by handler missing constant fields when selecting from a view (MDEV-36307)
Data Definition - Alter Table
Incorrect error handling on DDL with FULLTEXT INDEX (MDEV-36061)
ALTER TABLE…SEQUENCE does not work correctly with InnoDB (MDEV-36038)
The server could crash when an UPDATE is about to commit concurrently with a CREATE INDEX that includes VIRTUAL columns (MDEV-36281)
ALTER TABLE…DROP COLUMN after a failed ALTER TABLE…DROP COLUMN could lead to a server crash (MDEV-36236)
GIS
Server aborts while deleting the record in spatial index (MDEV-35420)
Upgrades
Upgrades fail on Windows (MDEV-36128)
OTHER
Field pointer may be uninitialized in fill_record (MDEV-36181)
Wrong results from tables with a single record and an aggregate (MDEV-35238)
Galera
With wsrep_ignore_apply_errors = 0, the node crashes due to assertion thd->is_error() failed in Sql_cmd_dml::prepare(), shown in the logs (MDEV-35946)
In some cases, if there are MDL locks (for example, when LOCK TABLE is executed), a node could get stuck in the system thread due to incorrect handling of metadata locks (MDL) in server code when a transaction was BF aborted. (MDEV-35941)
Regression after the fix for MDEV-31413 - sometimes the server crashes with an assertion in wsrep::transaction::before_rollback(), for example when using OPTIMIZE TABLE on an ARIA table with wsrep_osu_method=RSU. (MDEV-32631)
In Galera, creating sequence with a small cache leads to signal 6 error: [ERROR] WSREP: FSM: no such a transition REPLICATING -> COMMITTED. (MDEV-33850)
Assertion `commit_trx' failed in innobase_commit() (ha_innodb.cc). An INSERT with sql_log_bin=0 is still replicated in Galera (per MDEV-7205), despite binary logging being disabled. This results in a partial binlog bypass, requiring a two-phase commit (2PC). During 2PC, the INSERT is first prepared (entering the PREPARED state in InnoDB), and on commit, the new assertion from MDEV-24035 fails, causing a crash with "Assertion 'commit_trx' failed" in logs. (MDEV-35658)
When a sequence is used and inserts run in parallel on multiple Galera nodes, a transaction may be aborted after passing certification. If it then attempts to roll back, the binlog statement cache—which includes reserved sequence values—may be written prematurely. This causes a crash with the diagnostic "WSREP: FSM: no such a transition REPLICATING -> COMMITTED" in the logs, as the transaction is supposed to replay and only write to the binlog during the final commit. (MDEV-33589)
After a corrupted table on one node triggers the cluster to vote to evict a node that failed a transaction, the current master can't commit any more and hangs. To avoid this crash in the future, the user should also update the galera library to version 26.4.21+. (MDEV-34998)
Creating partitioned tables is disallowed when wsrep_osu_method=TOI and wsrep_strict_ddl=ON, preventing alteration or deletion of partitioned tables. (MDEV-27861)
Attempting to create a CONNECT engine table results in "non-InnoDB sequences in Galera cluster" error message in logs due to an incorrect engine check. (MDEV-35748)
Build fails with cmake 4.0.0 due to wsrep (MDEV-36422)
A Galera node may hang due to improper mutex handling: a thread held lock_sys.wait_mutex while triggering a streaming replication rollback, which also tried to acquire THD::LOCK_thd_kill, leading to incorrect mutex usage. In debug versions, this leads to diagnostics like "safe_mutex: Found wrong usage of mutex 'wait_mutex' and 'LOCK_thd_data'", but in both debug and release versions, there is some probability that the node may hang. (MDEV-36509)
Partitioning
corruption when query cache cannot allocate block (MDEV-34075)
Data Manipulation - Update
Stack looping and SIGSEGV in Item_args::walk_args on UPDATE (MDEV-31647)
Server
Server crash in find_field_in_tables, Assertion `name' failed in find_field_in_table_ref (MDEV-25012)
Server crash when inserting from derived table containing insert target table (MDEV-32086)
MariaDB effectively running as root CAP_DAC_OVERRIDE (MDEV-36229)
Build fails with cmake 4.0 (MDEV-36506)
Plugin - Audit
Long server_audit_file_path causes buffer overflow (MDEV-36245)
Security
Fixes for the following security vulnerabilities:
Changelog
For a complete list of changes and bugfixes made in MariaDB 10.6.22, with links to detailed information on each push, see the changelog.
Contributors
For a full list of contributors to MariaDB 10.6.22, see the MariaDB Foundation release announcement.
This page is licensed: CC BY-SA / Gnu FDL
Last updated
Was this helpful?