Release date: 8 May 2025
MariaDB 10.5 is a previous stable series of MariaDB, maintained until June 2025. It is an evolution of MariaDB 10.4 with several entirely new features not found anywhere else and with backported and reimplemented features from MySQL.
MariaDB 10.5.29 is a Stable (GA) release.
Thanks, and enjoy MariaDB!
Incorrect undo logging for indexes on virtual columns whose index ID does not fit in 32 bits ()
The untested ha_spider::index_first_internal constructs broken queries ()
Unexpected error 1264 'Out of Range Value for Column' when inserting into ... select ... from a spider table ()
Tests calling the udf spider_copy_tables fail with --view-protocol ()
ALTER TABLE…SEQUENCE does not work correctly with InnoDB ()
Server aborts while deleting the record in spatial index ()
Upgrades fail on Windows ()
Field pointer may be uninitialized in fill_record ()
Wrong results from tables with a single record and an aggregate ()
updated to 26.4.22
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 ()
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. ()
Regression after the fix for - 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. (
corruption when query cache cannot allocate block ()
Stack looping and SIGSEGV in Item_args::walk_args on UPDATE ()
Server crash in find_field_in_tables, Assertion `name' failed in find_field_in_table_ref ()
Server crash when inserting from derived table containing insert target table ()
MariaDB effectively running as root CAP_DAC_OVERRIDE ()
Build fails with cmake 4.0 ()
Long server_audit_file_path causes buffer overflow ()
group by handler missing constant fields when selecting from a view ()
Fixes for the following :
For a complete list of changes made in MariaDB 10.5.29, with links to detailed information on each push, see the .
For a full list of contributors to MariaDB 10.5.29, see the .
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)
This page is licensed: CC BY-SA / Gnu FDL