MariaDB 11.7.2 Release Notes
Download Release Notes Changelog Overview of 11.7
Release date: 13 Feb 2025
MariaDB 11.7.2 is a Stable (GA) release. It is an evolution of MariaDB 11.6 with several entirely new features.
MariaDB 11.7 is a rolling release. One is expected to upgrade to MariaDB 11.8.2, there will be no 11.7.3.
Thanks, and enjoy MariaDB!
Storage Engines
Fix possible InnoDB hang while running out of buffer pool ()
Fix assertion failure on cascading foreign key update of table with vcol index in parent ()
Fix potential issue in secondary Index with ROW_FORMAT=COMPRESSED and Change buffering enabled ()
Fix possible crash on DELETE from a HEAP table ()
Fix possible Spider thread hang in 'Update' state on 2nd INSERT ()
Fix possible crash on bootup in spider_sys_open_table «ext-issue»«», «ext-issue»«» ()
44 new added. These are aliases for MySQL collations to make it easier to replicate from MySQL to MariaDB ()
The includes a new column, COMMENT which contains information about which collation the alias refers to.
Fix assertion falilure and possible index corruption with unique key and nopad collation without DESC or HASH keys ()
Fix incorrect formatting of timestamp during parsing of a binary log, causing point in time recovery discrepancies ()
can now correctly process more than one logfile when --stop-datetime is specified ()
Setting pseudo_thread_id to a value exceeding 4 bytes previously resulted in truncation when written to the binary log ()
Fix server crash in get_sort_by_table/make_join_statistics after INSERT into a view with ORDER BY ()
Fix failing assertion causing disruption and replication failure ()
Conditions with SP local variables are now pushed into derived table. Previous behaviour caused slow performance and table scans instead of using the pushed down condition ()
History is now stored on the same partitions on different Galera nodes when system versioning is enabled ()
Fix possible hang or crash during InnoDB purge with HASH indexes during ALTER TABLE ()
EXCHANGE PARTITION now works for tables with unique blobs ()
updated to 26.4.21
NOTE: Includes increasing the GCS protocol version, which prevents downgrades of individual nodes in the cluster as soon as all nodes have been updated
Fix streaming replication transaction crash with innodb_snapshot_isolation ()
For an authentication with the the password of the CREATE USER statement is now masked in the audit log ()
MariaDB Audit now detects all DCLs forms for masking a password ()
Adding a regular index on a vector column leads to invalid table structure ()
Vector values become zero after / restore, impacting data integrity for vector columns. ()
Server can crash when a SELECT query is including a DISTINCT and ORDER BY, and a vector index is used ()
Fix possible crash where server could not construct a geomery object from the input ()
Fix trigger created with "" which is adding rows to another table using "FOR EACH ROW insert into table2(id, name) values (NEW.id, NEW.name);" that did not work correctly when if bulk inserts are used by the application. Only the first row of the bulk insert would be added to the table ()
Fixes for the following :
For a complete list of changes made in , with links to detailed
information on each push, see the .
For a full list of contributors to , see the .
This page is licensed: CC BY-SA / Gnu FDL