E-book: A Practical Guide to AI and Vector Search in Relational Databases
Read Now
Download MariaDBContact Us

Release Notes for MariaDB Enterprise Server 10.6.24-20

MariaDB Enterprise Server 11.6.24-20 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.6, released on 2025-12-11

Download Release Notes Changelog Overview of Enterprise Server 10.6

Release date: 11 Dec 2025

MariaDB Enterprise Server 10.6.24-20 is a maintenance release of MariaDB Enterprise Server 10.6. This release includes a variety of fixes.

Backports

  • Two new fields are available via SHOW REPLICA STATUS (MENT-2129)

    1. Connects_Tried, which provides the number of attempts the replica has made to connect to the primary, and

    2. Master_Retry_Count, which provides the number of times the replica will attempt to connect to a primary before giving up.

  • Add the server option --replicate-rewrite-db to system variables and SHOW REPLICA STATUS (backport of MDEV-15530) (MENT-2421)

Changes in Storage Engines

  • This release incorporates MariaDB ColumnStore engine version 23.10.6

Notable changes

  • 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

  • Due to the impending EOL of Windows 10 22H2, and Windows 11 23H2, this will be the last release supporting these releases

  • The HashiCorp Key Management Plugin has been updated to provide robust stability against Vault communication failures:

    • The plugin is now configured to use cached keys for all communication errors (not just timeouts), ensuring continuous operation when the Vault server is temporarily unreachable.

    • The default setting for using the cache on errors is now ON.

    • The default key cache timeout (hashicorp_key_management_cache_timeout) has been increased to its maximum practical value (e.g., one year in milliseconds), maximizing key availability in the cache during extended service interruptions. (MENT-1582)

Issues Fixed

Can result in hang or crash

  • Assertion `table_share->tmp_table != NO_TMP_TABLE || m_lock_type == 1' failed upon REBUILD PARTITION (MDEV-20498)

  • Spider: Assertion `inited==RND' failed in handler::ha_rnd_end on DELETE (MDEV-26540)

  • Several bugs in SPATIAL INDEX page splitting logic could crash InnoDB if the PRIMARY KEY or the SPATIAL data is variable-length. (MDEV-27675)

  • Server hang with innodb_file_per_table=0, innodb_undo_tablespaces=0 (MDEV-29930)

  • InnoDB could crash if the definition of the InnoDB persistent statistics tables were incorrect. (MDEV-31740)

  • Server crash on cleanup of non-fully-constructed-due-to-an-error CTE (MDEV-32308)

  • Mariadb server crashed during insert (MDEV-36134)

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

  • Fixed crashing bug when inserting into a tables with several nextval(sequence) default values. (MDEV-37172)

  • Inconsistency detected - create sequence (MDEV-37366)

  • Parallel replica worker crashes during backup at retrying (MDEV-37453)

  • Fixed a problem where the server would crash with a segfault when trying to drop duplicate domain ids in the same command (MDEV-37885), e.g. FLUSH BINARY LOGS DELETE_DOMAIN_ID=(0), BINARY LOGS DELETE_DOMAIN_ID=(0)

  • Item_func_hex doesn't check for max_allowed_packet (MDEV-37947)

  • MDL conflict between XA and DDL in MariaDB Enterprise Cluster (MENT-2405)

  • Race of rolling back and committing transaction to binlog (MENT-2448)

  • For large transactions (i.e. those whose data exceeds the binlog_cache_size limit and spills into tmp files), provides a general performance improvement and fixes a bug that would lead to binlog corruption where the large transaction would have its GTID written into the binary log, without any additional transaction data, if the server's --tmp-dir was full. (MENT-2451)

  • Bug in MariaDB Enterprise Backup where it would crash during the 'maria_recovery' part. This could happen if server was doing repair or creating indexes while the backup was running (MENT-2463)

  • With --encrypt-binlog=ON if a node fails to apply a writeset it will crash the whole cluster due to a bug in Galera library encryption handling. Fixed in Galera library. (MENT-2474)

Can result in unexpected behaviour

  • ALTER TABLE could fail to update InnoDB persistent statistics. (MDEV-35163)

  • ALTER TABLE tbl_a ADD PARTITION (PARTITION pt2) MSAN uninitalized read (MDEV-36723)

  • mariadb-dump -T did not encode table names like the server did for frm files, so some tables can be created in the server, but not dumped with mariadb-dump -T, for example, a table con on Windows. (MDEV-37483)

  • CHECK TABLE…EXTENDED could flag bogus corruption on a column prefix index. (MDEV-37659)

  • very long query cannot be killed quickly (MDEV-37938)

  • If the server was killed during an operation that creates a .ibd file, such as TRUNCATE TABLE, it could fail to recover. (MDEV-37994)

  • InnoDB partition table disallow local GTIDs (MENT-2367)

  • If the user specifies some tls-related parameters in spider table creation with odbc/mariadb backend, these parameters could be ill-formatted in the odbc connection string, causing them to be ignored by the driver. (MENT-2407)

  • innochecksum misinterprets doublewrite buffer pages (MENT-2459)

Related to install and upgrade

  • #2 Assertion `binlog_table_maps == 0 || locked_tables_mode == LTM_LOCK_TABLES' failed in THD::reset_for_next_command (MDEV-22915)

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

  • Wrong results for self-touching shapes. (MDEV-31499)

  • Assertion `marked_for_read()' fails on slave upon RBR with binlog_row_image=MINIMAL (MDEV-31678)

  • UBSAN: nullptr-with-nonzero-offset/pointer-overflow in row_log_apply_ops (MDEV-37626)

  • The parameter innodb_trx_rseg_n_slots_debug was removed. (MDEV-37672)

  • During workload after crash recovery, an incorrect (too large) innodb_buffer_pool_pages_dirty could be reported. (MDEV-37677)

  • Galera-26.4.24 fails buid package due to galera_check timeout on some s390x platforms (MDEV-37691)

  • This only affects debug instrumented builds and tests that use the debug instrumentation. (MDEV-37724)

  • Lock checks for secondary indexes were unnecessarily accessing some history and could access freed BLOB pages that correspond to column prefixes. (MDEV-37753)

  • Backport "Systemd: Restart on OOM" fix to 10.6 (MDEV-37780)

  • Threadpool - debug assertion thread_group->active_thread_count >=0, from TP_connection_generic::wait_begin (MDEV-37902)

  • Merge applicable changes from InnoDB 8.4.7 (MDEV-37922)

  • Most of server Audit v2 tests are disabled and never run (MENT-1223)

  • The authentication plugin caching_sha2_password has been added, not loaded by default (MENT-2480)

Unexpected results

  • Replicated REPAIR TABLE writes an error in the log when normal REPAIR does not (MDEV-33184)

  • Spider: XA COMMIT ONE PHASE fails with "This xid does not exist" (MDEV-37829)

Changelog

For the complete list of changes in this release, see the changelog.

Platforms

In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.6.24-20 is provided for:

  • AlmaLinux 8 (x86_64, ARM64)

  • AlmaLinux 9 (x86_64, ARM64)

  • AlmaLinux 10 (x86_64, ARM64)

  • Debian 12 (x86_64, ARM64)

  • Microsoft Windows (x86_64) (MariaDB Enterprise Cluster excluded)

  • Oracle Linux 8 (x86_64, ARM64)

  • Oracle Linux 9 (x86_64, ARM64)

  • Oracle Linux 10 (x86_64, ARM64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Red Hat Enterprise Linux 9 (x86_64, ARM64, PPC64LE)

  • Red Hat Enterprise Linux 10 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • Rocky Linux 9 (x86_64, ARM64)

  • Rocky Linux 10 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 22.04 (x86_64, ARM64)

  • Ubuntu 24.04 (x86_64, ARM64)

  • Microsoft Windows (x86_64) (Without MariaDB Enterprise Cluster (Galera) support)

  • Red Hat UBI 8 (x86_64, ARM64)

    • Red Hat UBI 8 is part of the Enterprise Server Docker Image. It does not support MariaDB Enterprise Cluster (Galera) or MariaDB ColumnStore.

Some components of MariaDB Enterprise Server are supported on a subset of platforms. See MariaDB Engineering Policies for details.

Installation Instructions

Upgrade Instructions

This page is: Copyright © 2025 MariaDB. All rights reserved.

PreviousWhat's New in MariaDB Enterprise Server 10.6?NextRelease Notes for MariaDB Enterprise Server 10.6.23-19

Last updated

Was this helpful?