Changelog for MariaDB Enterprise Server 10.6.22-18

MariaDB Enterprise Server 10.6.22-18 is a maintenance release of MariaDB Enterprise Server 10.6. For the categorized highlights and other details of this release, see the release notes.

MariaDB Enterprise Server 10.6.22-18 was released on 11 Jun 2025.

Changes

• (MDEV-36519) Q2 2025 release merge

• (MENT-2301) New user variable, analyze_max_length, default value 4G. Any field that is bigger than this value in bytes will be ignored by ANALYZE TABLE PERSISTENT to not collect statistics for long char/varchars unless it is specified in FOR COLUMNS(). 

• (MENT-2311) SBOM now includes 'license' and 'copyright' information, improving security compliance and dependency tracking.

Issues Fixed

• (MDEV-36115) Assertion InnoDB searching row in wrong partition for multiple system versioned DELETE with same timestamp and same multistatement transaction
• (MDEV-35909) For Galera, ALTER SEQUENCE crash DB server
• (MDEV-36061) Incorrect error handling on DDL with FULLTEXT INDEX
• (MDEV-36038) ALTER TABLE…SEQUENCE does not work correctly with InnoDB
• (MDEV-36122) Race conditions between ALTER TABLE or OPTIMIZE TABLE and the purge of transaction history were fixed.
• (MDEV-35420) Server aborts while deleting the record in spatial index
• (MDEV-36281) The server could crash when an UPDATE is about to commit concurrently with a CREATE INDEX that includes VIRTUAL columns
• (MDEV-36128) Upgrades fail on Windows
• (MDEV-33167) ASAN errors in dict_sys_t::load_table / get_foreign_key_info after failing to load a table
• (MDEV-36236) ALTER TABLE…DROP COLUMN after a failed ALTER TABLE…DROP COLUMN could lead to a server crash
• (MDEV-36181) Field pointer may be uninitialized in fill_record
• (MDEV-36182) revert incorrect 5.14 kernel warnings and correct liburing interface usage
• (MDEV-36359) A primary server could crash when a semi-sync connection is stopped, if the primary previously disabled semi-sync replication while the connection was already up (and `rpl_semi_sync_master_wait_no_slave=0`).
• (MDEV-36613) Incorrect undo logging for indexes on virtual columns whose index ID does not fit in 32 bits
• (MDEV-35946) 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-35941) 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-32631) 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-34891) SST failure occurs when gtid_strict_mode is enabled under high load, such as OLTP load is active on the primary node. A typical symptom of this error is the presence of the diagnostic "[ERROR] mariadbd: Error writing file 'binlog'", in the debug version it is also possible to crash on assertion in the wsrep::transaction::before_rollback() function with the message "Assertion `state() == s_executing || state() == s_preparing || state() == s_prepared || state() == s_must_abort || state() == s_aborting || state() == s_cert_failed || state() == s_must_replay' failed".
• (MDEV-33850) In Galera, creating sequence with a small cache leads to signal 6 error: [ERROR] WSREP: FSM: no such a transition REPLICATING -> COMMITTED.
• (MDEV-36116) Under high load wsrep internal thread may terminate due to memory pressure conditions, but this is not a crash, however in debug version user may encounter assertion in wsrep_to_isolation_begin() function with following message: "int wsrep_to_isolation_begin(THD*, const char*, const char*, const TABLE_LIST*, const Alter_info*, const key_array*, const HA_CREATE_INFO*): Assertion `(0)' failed."
• (MDEV-35658) 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-33589) 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-36509) 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-34075) corruption when query cache cannot allocate block
• (MDEV-31647) Stack looping and SIGSEGV in Item_args::walk_args on UPDATE
• (MDEV-25012) Server crash in find_field_in_tables, Assertion `name' failed in find_field_in_table_ref
• (MDEV-36245) Long server_audit_file_path causes buffer overflow
• (MDEV-32086) Server crash when inserting from derived table containing insert target table
• (MDEV-35962) CREATE INDEX fails to heal a FOREIGN KEY constraint
• (MDEV-36180) Doublewrite recovery of innodb_checksum_algorithm=full_crc32 page_compressed pages does not work
• (MDEV-35579) With WolfSSL server does not chose best TLSv1.3 cipher offered by client
• (MDEV-31122) Segfault on concurrent ALTER and SELECT for partitioned table
• (MDEV-32619) ST_PointFromWKB ignores SRID argument and always creates the POINT with 0 for it's SRID
• (MDEV-36268) mariadb-dump used wrong quoting character
• (MENT-2081) 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) 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-35807) MDEV-32157 intended to fix spider wrapper so that it is case insensitive, among other things. However that fix was incomplete, as the udf spider_direct_sql may still require case sensitivity. MDEV-35807 fixes this.
• (MDEV-27861) Creating partitioned tables is disallowed when wsrep_osu_method=TOI and wsrep_strict_ddl=ON, preventing alteration or deletion of partitioned tables.
• (MDEV-35748) 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-36639) innodb_snapshot_isolation=1 gives error for not committed row changes
• (MENT-2235) Aria engine: log initialization failed
• (MENT-2089) MariaDB Backup returns with an error like "Error on file ./test/t1#P#p513.MYD open during `test`.`t1` table copy for partitioned MyISAM tables when running out of file handles
• (MDEV-36413) User without any privileges to a sequence can read from it and modify it via column default
• (MDEV-36380) User has unauthorized access to a sequence through a view with security invoker
• (MDEV-36248) Connect crashes server because of duplicate 'free()' in GetUser
• (MENT-2156) Failure in the galera_sr.galera_xa_multi_se test due to bug in server code, which causes 'used ENGINE (in Galera cluster)' error message in the log and this caused by the fixes for the server code (related to galera) were not fully migrated from the CS edition to ES.
• (MDEV-36026) Problem with INSERT SELECT on NOT NULL columns while having BEFORE UPDATE trigger
• (MDEV-36138) Server null-pointer crash at startup when tmptables left in --tmpdir
• (MDEV-35813) Performance regression in INSERT…SELECT due to unnecessarily making InnoDB log durable.
• (MDEV-36684) main.mdl_sync fails under valgrind (test for Bug#42643)
• (MDEV-31977) When we compile MariaDB 10.6.11 with asan, we failed to run the testcase of rocksdb.
• (MDEV-36730) Spuštění nežádoucího triggeru, Zmatení engine, generování null
• (MDEV-36516) galera_3nodes.galera_gtid_2_cluster test failed on 10.5 (these are flaws in the test itself; the fix did not require changing the main server code)
• (MDEV-36666) atomic.alter_table still times out often
• (MDEV-36685) CREATE-SELECT may lose in binlog side-effects of stored-routine
• (MDEV-36477) Spider tests with view protocol fail with "Failed to drop view: 0: "
• (MDEV-36478) spider basic_sql tests with view protocol fail with mismatching found_rows() output
• (MDEV-36633) spider/bugfix.mdev_33434 fails with --view-protocol
• (MDEV-36476) Spider tests hanging with --view-protocol
• (MDEV-36304) mariabackup.partial test fails with InnoDB: Missing FILE_CREATE, FILE_DELETE or FILE_MODIFY before FILE_CHECKPOINT
• (MDEV-36078) PCRE2 10.45 breaks main.func_regexp_pcre due to change in PCRE
• (MDEV-35727) main.mysql-interactive fails in buildbot on debian
• (MDEV-35653) Assertion `commit_trx' failed in int innobase_commit(handlerton*, THD*, bool)
• (MDEV-36412) Concerns compilation issue on community edition for x86_64 with X32 ABI
• (MDEV-36618) galera.galera_as_slave_nonprim test: result content mismatch
• (MDEV-36620) galera_toi_ddl_nonconflicting test failure
• (MDEV-36681) PAM (v2) tests not running successfully on install VMs
• (MDEV-36372) Compilation error with the "-DPLUGIN_PARTITION=NO" option.
• (MDEV-36393) Test failure in galera_sr.GCF-572 caused by merge changes between branches.
• (MDEV-35934) Duplicate of the MDEV-33850
• (MDEV-34501) SIGSEGV in pfs_start_mutex_wait_v1, strlen_avx2, or strlen_evex from safe_mutex_lock on CREATE DEFINER when using skip-grant-tables
• (MDEV-36341) UBSAN: runtime error: applying non-zero offset 138116761973048 to null pointer (FederatedX)
• (MDEV-36015) AUTO_INCREMENT values of DOUBLE or FLOAT type may be read incorrectly
• (MDEV-29775) Assertion `0' failed in void Protocol::end_statement() when adding data to the MyISAM table after setting wsrep_mode=replicate_myisam
• (MDEV-24485) galera.galera_bf_kill_debug MTR failed: A long semaphore wait
• (MDEV-28209) New mysql_upgrade message on minor-only upgrades is confusing
• (MDEV-36510) InnoDB fails to compile with clang++-20
• (MDEV-36464) Galera test failure on galera_3nodes.galera_gtid_2_cluster
• (MDEV-4151) Error message on an attempt of RPM upgrade from one major version to another mixes up MySQL and MariaDB
• (MDEV-36347) UBSAN: plugins.auth_v0100 - runtime error: call to function do_auth_0x0100 through pointer to incorrect function type
• (MDEV-36427) FTBFS with libxml2 2.14.0
• (MDEV-36507) fix dbug_print_row concurrent access
• (MDEV-35959) Assertion `*str != '\0'' failed in my_message_sql after a Spider error
• (MDEV-36441) Spider tests fail with extra warnings about same server when run with --view-protocol
• (MDEV-36454) spider tests wrong count of spider_direct_aggregate when run with --view-protocol
• (MDEV-36442) spider tests with --view-protocol fail with diff SELECT argument FROM mysql.general_log ...
• (MDEV-36452) Column name output in --view-protocol spider tests with udf and CASE
• (MDEV-35721) UBSAN: runtime error: -nan is outside the range of representable values of type 'unsigned long long' in Index_statistics::set_avg_frequency on INSERT or SHOW INDEX
• (MDEV-36179) Assertion `0' failed in virtual bool Type_handler_row::Item_save_in_value(THD*, Item*, st_value*) const
• (MDEV-35620) UBSAN: runtime error: applying zero offset to null pointer in _ma_unique_hash, skip_trailing_space, my_hash_sort_mb_nopad_bin and my_strnncollsp_utf8mb4_bin
• (MDEV-36217) New MY_RELAX_CPU dependency on riscv_pause breaks riscv64 build (Regression from MDEV-35827)
• (MDEV-33295) The test innodb.doublewrite occasionally fails
• (MDEV-36208) dbug_print_table_row is broken: prints empty rows in debugger
• (MDEV-36270) mariabackup.incremental_compressed fails in 10.11+
• (MDEV-34489) innodb.innodb_row_lock_time_ms fails
• (MDEV-36156) building MSAN -stdlib=libc++ test requires -fsanitize=memory
• (MDEV-26652) xa transactions binlogged in wrong order
• (MDEV-35117) Error message "ERROR 1815 (HY000): Internal error: st_distance_sphere' could be improved
• (MDEV-36229) MariaDB effectively running as root CAP_DAC_OVERRIDE
• (MDEV-27126) my_getopt compares option names case sensitively
• (MDEV-36422) Build fails with cmake 4.0.0 due to wsrep
• (MDEV-36506) Build fails with cmake 4.0
• (MDEV-34738) Upgrade MariaDB from 10.11 to 11.4 may cause Galera cluster to fail to start due to an issue with the socket.ssl_cipher setting in wsrep_provider_options. To avoid this bug, we advise using version 11.4 with galera library 26.4.21 or later.
• (MDEV-36378) The deprecated parameter innodb_purge_rseg_truncate_frequency is not being recognized
• (MDEV-35436) dict_stats_fetch_from_ps() unnecessarily holds exclusive dict_sys.latch
• (MDEV-36226) Stall and crash when page cleaner fails to generate free pages during Async flush
• (MDEV-36324) The untested ha_spider::index_first_internal constructs broken queries
• (MDEV-35238) Wrong results from tables with a single record and an aggregate
• (MDEV-35874) Unexpected error 1264 'Out of Range Value for Column' when inserting into ... select ... from a spider table
• (MDEV-36307) group by handler missing constant fields when selecting from a view
• (MDEV-36335) Tests calling the udf spider_copy_tables fail with --view-protocol