githubEdit

Changelog 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

triangle-exclamation

Download Release Notes Changelog Overview of MariaDB Enterprise Server 10.6

MariaDB Enterprise Server 10.6.24-20 is a Stable (GA) maintenance release of MariaDB Enterprise Server 10.6. For the categorized highlights and other details of this release, see the release notes.

Release date:

Changes

  • Backport MDEV-9804 "Implement a caching_sha2_password plugin" for MariaDB Enterprise Server 10.6 (MENT-2480arrow-up-right)

  • Two new fields are available via SHOW REPLICA STATUS:

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

    • Master_Retry_Count, which provides the number of times the replica will attempt to connect to a primary before giving up. (MENT-2129arrow-up-right)

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

  • Spider dev documentation (MDEV-30265arrow-up-right)

Issues Fixed

  • 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-36545arrow-up-right)

  • Inconsistency detected - create sequence (MDEV-37366arrow-up-right)

  • InnoDB could crash during the crash recovery of a corrupted database. (MDEV-37412arrow-up-right)

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

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

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

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

  • MDL conflict between XA and DDL in Galera cluster (MENT-2405arrow-up-right)

  • Cherry Pick MDEV-37541 - Race of rolling back and committing transaction to binlog (MENT-2448arrow-up-right)

  • 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-2451arrow-up-right)

  • Cherry-Pick MDEV-37138 "innochecksum misinterprets doublewrite buffer pages" (MENT-2459arrow-up-right)

  • Backport fix for MDEV-36860 to ES 10.6 (MENT-2463arrow-up-right)

  • Backport the fix for MDEV-34744 to Enterprise Server 10.6 (MENT-2465arrow-up-right)

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

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

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

  • Tested on 10.6.24, the issue is not reproducible anymore. (MDEV-30456arrow-up-right)

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

  • SIGSEGV in maria_rtree_split_page | maria_rtree_add_key (MDEV-31766arrow-up-right)

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

  • Mariadb server crashed during insert (MDEV-36134arrow-up-right)

  • Fix for unstable mtr test (MDEV-36949arrow-up-right)

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

  • The minimum value of the parameter innodb_ft_min_token_size was increased to 1, similar to the parameter ft_min_word_len. (MDEV-37423arrow-up-right)

  • Parallel slave worker crashes During Backup at retrying (MDEV-37453arrow-up-right)

  • decimal_digits_t trips GCC -Wconversion (MDEV-37477arrow-up-right)

  • 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-37483arrow-up-right)

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

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

  • The HashiCorp Key Management Plugin has been updated to provide robust stability against Vault communication failures (MENT-1582arrow-up-right)

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

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

  • Wrong hardcoded default for GIT_REMOTE_ORIGIN_URL in ES (MENT-2393arrow-up-right)

  • 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. Concerns only Enterprise Server as only it enables Galera encryption, all versions: 10.5, 10.6, 11.4, 11.8 (MENT-2474arrow-up-right)

  • A misplaced debug assertion could fail due to a race condition. In MariaDB Server 11.8.1, this bug had already been fixed as part of MDEV-35049. (MDEV-20203arrow-up-right)

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

  • 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-26599arrow-up-right)

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

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

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

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

  • Recovery of Aria transactional tables did not work in big-endian machines like s390x and Sparc (MDEV-34914arrow-up-right)

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

  • UBSAN: runtime error: load of value 1341112147, which is not a valid value for type 'enum enum_schema_tables' in optimize_for_get_all_tables and get_all_tables and on SELECT from I_S geometry_columns (MDEV-35713arrow-up-right)

  • only mtr test has been fixed (MDEV-36710arrow-up-right)

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

  • galera.galera_sst_encrypted LeakSanitizer: detected memory leaks (MDEV-37206arrow-up-right)

  • SIGSEGV in srv_printf_innodb_monitor (MDEV-37360arrow-up-right)

  • It appears that some error conditions don't store error information in the Diagnostics_area.

    • For example when table_def::compatible_with() check fails error message is stored in Relay_log_info instead.

    • This results in optimistically identical votes and zero error buffer size breaks wsrep-lib logic as it relies on error buffer size to decide whether voting took place.

    • To account for this, first try to obtain error info from Relay_log_info, then fallback to Diagnostics_area. If that fails use some random data to distinguish this condition from success.

    • This requires bumping of the application protocol to 8 since vote message generation algorithm has changed. (MDEV-37494arrow-up-right)

  • myisamchk -V crashes (MDEV-37505arrow-up-right)

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

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

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

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

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

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

  • Fixed a problem where the server would crash with a segfault when trying to drop duplicate domain ids in the same command, e.g.

  • FLUSH BINARY LOGS DELETE_DOMAIN_ID=(0), BINARY LOGS DELETE_DOMAIN_ID=(0) (MDEV-37885arrow-up-right)

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

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

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

spinner

Last updated

Was this helpful?