MariaDB 10.6.24 Release Notes
MariaDB 10.6.24 is a Stable (GA) release of MariaDB Community Server 10.6, released on 2025-11-06
Download Release Notes Changelog Overview of 10.6
Alternate download from mariadb.org
Release date: 6 Nov 2025
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.24 is a Stable (GA) release.
For an overview of MariaDB 10.6 see the MariaDB 10.6 Changes & Improvements page.
Thanks, and enjoy MariaDB!
Notable Items
Storage Engines
InnoDB
InnoDB could crash after a DROP TABLE, TRUNCATE TABLE, OPTIMIZE TABLE or a table-rebuilding ALTER TABLE if innodb_adaptive_hash_index entries existed in the table. (MDEV-26599)
InnoDB could crash if the definition of the InnoDB persistent statistics tables were incorrect. (MDEV-31740)
ALTER TABLE could fail to update InnoDB persistent statistics. (MDEV-35163)
InnoDB could crash during the crash recovery of a corrupted database. (MDEV-37412)
CHECK TABLE…EXTENDED could flag bogus corruption on a column prefix index. (MDEV-37659)
During workload after crash recovery, an incorrect (too large) innodb_buffer_pool_pages_dirty could be reported. (MDEV-37677)
Lock checks for secondary indexes were unnecessarily accessing some history and could access freed BLOB pages that correspond to column prefixes. (MDEV-37753)
Aria
Recovery of Aria transactional tables did not work in big-endian machines like s390x and Sparc (MDEV-34914)
Spider
Spider: XA COMMIT ONE PHASE fails with "This xid does not exist" (MDEV-37829)
MyISAM
myisamchk -V crashes (MDEV-37505)
Full-text Search
InnoDB could potentially crash if there is any lock conflict on an internal FTS_%_CONFIG table of a FULLTEXT INDEX while one of the INFORMATION_SCHEMA views INNODB_TRX, INNODB_LOCKS, or INNODB_LOCK_WAITS are being accessed. (MDEV-36545)
The minimum value of the parameter innodb_ft_min_token_size was increased to 1, similar to the parameter ft_min_word_len. (MDEV-37423)
Galera
Galera updated to 26.4.24
NOTE: Includes increasing the GCS protocol version, which prevents downgrades of individual nodes in the cluster as soon as all nodes have been updated
MariaDB Cluster server crash during insert when replication filters are used (MDEV-36134)
Inconsistency detected - create sequence (MDEV-37366)
Parser
very long query cannot be killed quickly (MDEV-37938)
GIS
Several bugs in SPATIAL INDEX page splitting logic could crash InnoDB if the PRIMARY KEY or the SPATIAL data is variable-length. (MDEV-27675)
Wrong results for self-touching shapes. (MDEV-31499)
Optimizer - CTE
Server crash on cleanup of non-fully-constructed-due-to-an-error CTE (MDEV-32308)
Sequences
Fixed crashing bug when inserting into a tables with several nextval(sequence) default values. (MDEV-37172)
Backup
Parallel slave worker crashes During Backup at retrying (MDEV-37453)
Scripts & Clients
mariadb-dump -Tdid not encode table names like the server did forfrmfiles, so some tables can be created in the server, but not dumped withmariadb-dump -T, for example, a tableconon Windows. (MDEV-37483)
Changelog
For a complete list of changes made in MariaDB 10.6.24, with links to detailed information on each push, see the changelog.
Be notified of new MariaDB Server releases automatically by subscribing to the MariaDB Foundation community announce 'at' lists.mariadb.org announcement list (this is a low traffic, announce-only list). MariaDB plc customers will be notified for all new releases, security issues and critical bug fixes for all MariaDB plc 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.
This page is licensed: CC BY-SA / Gnu FDL
Last updated
Was this helpful?

