Download Release Notes Changelog Overview of 11.8

^{Alternate download from mariadb.org}

Release date: 14 Nov 2025

MariaDB 11.8.5 is a Stable (GA) release. It is an evolution of MariaDB 11.7 with several entirely new features.

MariaDB 11.8 is a long-term release.

Thanks, and enjoy MariaDB!

Notable Items

• : This issue caused a partial data deletion when using the DELETE statement on MyISAM or Aria tables under specific conditions. InnoDB tables are not affected by this issue. Specifically, when a DELETE statement included a WHERE clause with a non-unique indexed column compared for equality with a literal (col=const) and the execution plan showed a "range" operation on that index, the query could fail to delete all matching rows. Users of MariaDB Community Server 11.8.4 are strongly advised to upgrade immediately to 11.8.5.

Changelog

For a complete list of changes made in MariaDB 11.8.5, with links to detailed information on each push, see the .

Release date: 13 Feb 2025

is a current long-term development series of MariaDB. It is an evolution of with several entirely new features.

is a release.

For an overview of see the page.

Thanks, and enjoy MariaDB!

Download Release Notes Changelog Overview of 11.8

Release date: 18 Dec 2024

MariaDB 11.8 is a long-term development series of MariaDB. It is an evolution of MariaDB 11.7 with several entirely new features.

MariaDB 11.8.0 is a single preview release. Features are to be considered previews, and none are guaranteed to make it into MariaDB 11.8.

The preview is available as a container quay.io/mariadb-foundation/mariadb-devel:11.8-preview.

For an overview of MariaDB 11.8, see the What is MariaDB 11.8? page.

Thanks, and enjoy MariaDB!

Notable Items

Vectors

• New function for calculating either a Euclidean or Cosine distance between two vectors, depending on the underlying index type ()

• aarch64 SIMD instructions now supported ()

Optimizer

• Expanded ()

  • Implement ()

  • Implement ()

  • Optimizer hints did not make it into the final release.

InnoDB

• Fix scalability with multiple threads ()

Importing

• The --no-autocommit option is now set by default to allow faster data loading by InnoDB, writing only one undo log for the whole operation ()

• has a new option --innodb-optimize-keys to delay creation of secondary indexes until after data load, resulting in faster loads. By default. ()

GIS

New GIS functions. These functions improve compatibility with MySQL 8.

• ()

• ()

• ()

• ()

Functions

• New function. Given a byte count, returns a string consisting of a value and the units in a human-readable format ()

Referential Integrity

• now also checks for referential integrity ()

Information Schema

• When querying the , that have the same name as a native function no longer generate a warning ()

Download Release Notes Changelog Overview of 11.8

^{Alternate download from mariadb.org}

Release date: 6 Aug 2025

MariaDB 11.8.3 is a Stable (GA) release. It is an evolution of MariaDB 11.7 with several entirely new features.

MariaDB 11.8 is a long-term release.

Thanks, and enjoy MariaDB!

Notable Items

Storage Engines

InnoDB

• After SET GLOBAL innodb_buffer_pool_size was aborted while attempting to shrink the buffer pool, executing SET GLOBAL innodb_adaptive_hash_index=ON could lead to corruption of the adaptive hash index. ()

• Fatal InnoDB error: Unknown error Temp file write failure ()

• When innodb_buffer_pool_size is being shrunk while there are no data pages cached, InnoDB could hang or crash. ()

• After a successful shrinking of innodb_buffer_pool_size, there will be no message about it in the server error log.

Aria

• Assertion when adding FK to MyISAM/Aria table with a vector index ()

Data Definition - Alter Table

• Adding (with ALTER TABLE) a UNIQUE constraint that is USING HASH to a table with foreign keys could've caused the table to become corrupted. ()

• DROP DEFAULT makes SHOW CREATE non-idempotent ()

Partitioning

• Server crashes in do_mark_index_columns instead of ER_DUP_ENTRY on partitioned table ()

• A replica would crash while replicating UPDATE and DELETE DML statements that target a table which previously had a partition that was converted to a separate table via ALTER TABLE .. CONVERT PARTITION .. TO TABLE. For example, if the command looked like ALTER TABLE t1 CONVERT PARTITION p1 TO TABLE t_new; the replica would crash when trying to update/deleterows in table t1 after running the command. ()

Data Definition - Create Table

• CREATE OR REPLACE with self-referencing CHECK hangs forever, cannot be killed ()

Server

• Segfault on INTERSECT ALL with UNION in Oracle mode ()

• In certain cases privileges on sequences were too restrictive, for example, SELECT on a table might've erroneously required INSERT privilege on a sequences ()

mariabackup

• This commit fixes a bug where Aria tables are used in (master->slave1->slave2) and a backup is taken on slave2. In this case it is possible that the replication position in the backup, stored in mysql.gtid_slave_pos, will be wrong. This will lead to replication errors if one is trying to use the backup as a new slave. ()

• Maria-backup would crash during the 'maria_recovery' part. This could happen if server was doing repair or creating indexes while the backup was running. ()

Optimizer

• MariaDB server crash when a query includes a derived table containing unnamed column. ()

• Crash in add_keyuses_for_splitting() when joining with a derived table ()

• Split Materialized code: last_refills is never set in 11.0+ ()

• Don't generate index_merge plans, if a column is present in both Secondary Key and Primary Key indexes and either of the indexes include it with DESC order (as the scan itself is not a ROR scan). ()

JSON

• Starting from 10.11.12, Incorrect handling of UTF-8 characters (and other character sets requiring more than a single byte representation) in the minimum/maximum positions of a table during the execution of ANALYZE TABLE tbl PERSISTENT FOR ALL resulted in an endless loop consuming more memory and prevented the server from terminating. ()

Galera

• updated to 26.4.23

• galera_3nodes.inconsistency_shutdown test occasionally hangs ()

• Galera-26.4.23 corrects an incompatibility with OpenZFS >= 2.3.0 enabling the use of galera on this filesystem.

Replication

• semi sync makes the master unresponsive when a replica is stopped ()

• parallel slave ALTER-SEQUNCE attempted to binlog out-of-order ()

• mysqldump --dump-slave always starts stopped slave ()

• Optimize Rows_log_event Reporting of Process Info ()

Stored routines

• Crash when calling stored function in FOR loop argument ()

Authentication and Privilege System

• ALTER TABLE require ALTER privilege on sequence from DEFAULT value expression ()

Locking

• Deadlock does not rollback transaction fully ()

Data Manipulation - Insert

• UNIQUE constraint that was USING HASH and UNIQUE constrant WITHOUT OVERLAPS could be violated under heavy load in READ COMMITTED transaction isolation mode. ()

Character Sets

• Changing the server character set in my.cnf could cause debian-start script to fail with "Illegal mix of collations" ().

Plugin - AWS key management

• aws_key_management compilation was previously broken, is now fixed. plugin can be compiled again. As before, -DNOT_FOR_DISTRIBUTION=ON is necessary to build it. ()

Packaging

• mariadb systemd mult-instance service was changed to not attempt changes to the permissions on its pam helper server. This prevented unconstructive behaviour and errors in the systemd journal when starting the mariadb@.service. ()

Sequences

• Remove the error codes added to 10.11 by the MDEV-36032 patch ()

XA

• DML committed within XA transaction block after deadlock error and implicit rollback ()

General

• Add option to not collect statistics for long char/varchars ()

• Packages for RHEL8 no longer depend on liburing. The RHEL8 kernel had insufficient kernel support so linking was an unneeded dependency. libaio was sufficient ()

• SLES 15 SP6 and SLES 15 SP7 are new packages in this release. Because of incompatibilities of packages between SLES service pack versions there are now separate packages for 15sp6 and 15sp7. An upgradeable repo file should include "sles/$releasever/$basearch" rather than the "sles15-amd64" or "sles/15/x86_64" path that may exist currently. (, )

Changelog

For a complete list of changes made in MariaDB 11.8.3, with links to detailed information on each push, see the .

is a long-term release, maintained until June 2028.

This list includes all features since the previous long-term release, (those introduced in the , and rolling releases, and in MariaDB 11.8).

Upgrading

• Note that if you are using system versioned tables, all rows and indexes has to be updated in these to use the extended timestamp range ('

Release date: 6 Nov 2025

MariaDB 11.8.4 is a release. It is an evolution of with several entirely new features.

is a .

Thanks, and enjoy MariaDB!

Notable Items

Storage Engines

InnoDB

• The InnoDB purge subsystem will no longer reset transaction identifiers in freshly inserted records, because it did severely hurt performance in some workloads. ()

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

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

• Workloads that are bound by innodb_log_file_size would write out unnecessarily many data pages in an attempt to advance the log checkpoint. (

Aria

• Recovery of Aria transactional tables did not work in big-endian machines like s390x and Sparc.()

• Failure to detect corruption during backups of Aria table ()

Connect

• BsonGet_String and JsonGet_String with a NULL argument resulted in an empty string warning. This now has an "Argument is NULL" warning. ()

Federated

• FederatedX error 10000 on multi-table UPDATE/DELETE ()

MyISAM

• myisamchk -V crashes ()

RocksDB

• Corrected python3 compatibility of myrocks_hotbackup thanks to contributor i18n.site ()

Spider

• Server may crash in spider bg mode if multiple queries are sent by spider bg threads consecutively ()

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

Full-text Search

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

• The minimum value of the parameter innodb_ft_min_token_size was increased to 1, similar to the parameter ft_min_word_len. ()

Optimizer

• Prevent MariaDB server crash when a query includes a derived table containing unnamed column. ()

• Crash when considering Split-Materialized plan ()

• Wrong result when split optimization is used for grouping with order by and limit ()

• Correlated derived table query merges can cause crashes, especially with prepared statements. ()

Sequences

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

Galera

• Setting wsrep_slave_threads causes thread hang when wsrep is not enabled ()

• MariaDB Cluster server crash during insert when replication filters are used ()

• Inconsistency detected - create sequence ()

• InnoDB partition table disallow local GTIDs in galera ()

Plugins

• Change several Plugin Maturity Levels ()

Plugin - Audit

• Wrong query_ids are logged by the server_audit plugin for inserts by triggers when multi-insert statements are used ()

• Fix server_audit rwlock Performance Schema instrumentation ()

Plugin - Hashicorp Key Management

• Hashicorp Plugin: enable key version caching by default ()

Plugin - userstat

• The number of concurrent connections reported by userstats, when enabled, is updated. ()

JSON

• Corrected the creation of views on JSON_TABLEs to require no special privileges. ()

• JSON_ARRAY_INTERSECT function crashes the server when called with empty json arrays ()

• View containing JSON_TABLE does not return JSON ()

• Wrong result json_table ()

Parser

• very long query cannot be killed quickly ()

Server

• LIMIT ROWS EXAMINED prematurely triggers during optimization ()

• Exchange partition with virtual columns fails ()

• ALTER TABLE allows adding unique hash key with duplicate values ()

• LOCATE(X,Y,NULL) is not NULL ()

Locking

• DDL in procedure propagates no locking to tables locked by DML ()

Partitioning

• Errors or assertion failure upon REPAIR on partitioned Aria table with misplaced rows ()

Platform RedHat

• On Fedora, RHEL, and derivatives, depend on the mysql-selinux-1.0.14 package that provides the correct selinux rules for the /usr/sbin/mariadbd that is installed. ()

Platform Windows

• On Windows, when MSI package is installed, with ADDLOCAL parameter passed to msiexec.exe, and Visual C++ Redistributable package is not installed on the target machine, installation may fail during "create database" step. ()

Stored routines

• Crash when calling stored function in FOR loop argument ()

• Fix crash by correctly updating SP instruction state after instruction re-parsing , preventing dangling reference. ()

GIS

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

• Wrong results for self-touching shapes. ()

Optimizer - CTE

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

Packaging

• A tmpfiles file will now create /run/mysqld path on Debian/Ubuntu packaged distributions. ()

• server cannot load client plugins on Debian ()

• Previous systemd warnings in recent systemd versions about uninitialised environment variables have been corrected. ()

• The PrivateDevices=false directive in the systemd service has been removed as it was an old kernel incompatibility that this directived worked around. With this, the MariaDB is restricted further. Those using InnoDB on raw devices will need to add an override for this. See https://mariadb.com/docs/server/server-management/starting-and-stopping-mariadb/systemd#useful-systemd-options (

Backup

• Parallel slave worker crashes During Backup at retrying ()

Scripts & Clients

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

• Using mytop with DBD-MariaDB and host=localhost specified resulted in an unexpected error because the driver did not expect a port 3306. Contribution thanks to Jean Weisbuch. ()

Authentication and Privilege System

• Backport “Implement a caching_sha2_password plugin” ()

Versioned Tables

• REPLACE on a precise-versioned table returns duplicate key error (ER_DUP_ENTRY) ()

Prepared Statements

• Parameterized PS converts error to warning, causes replication problems ()

Admin statements

• Assertion failure in online_alter_log_row or server hang upon replicating REPAIR on mysql.gtid_slave_pos ()

Data Definition - Create Table

• Innodb did not handle case-sensitivity on Windows correctly prior to this fix in its data dictionary, converting all names to lowercase. This resulted in inconsistency, if data directory was in case-sensitive NTFS directory, as well as in situations when data directory was copied from Windows to Unix systems. This is fixed in this patch. ()

mariabackup

• Fixed bug in maria-backup where maria-backup would crash during the 'maria_recovery' part. This could happen if server was doing repair or creating indexes while the backup was running. ()

Replication

• Fix --master-retry-count=0 not infinite as described ()

• Ensure that Annotate_rows is always written direct after GTID information, before any table_map events. Before this patch the event could be written in a random position in the binary log. This change make the place of the Annotate_rows event predictable. When mixing transactional and not transactional tables in the same transaction, the Annotate rows event was not always written in the case of a rollback. This is now fixed. ()

• ALTER TABLE ... ENGINE=MRG_MyISAM is now properly logged as an DDL. This ensure that the changed MERGE table cannot be used by a slave thread until after the ALTER command has been executed. ()

Configuration

• Galera galera_new_cluster scipt and its systemd interactions was rewritten to avoid selinux errors. This will require the mysql-selinux-1.0.14+ version that is a dependency of the server in RPM+selinux distributions. ()

Changelog

For a complete list of changes made in MariaDB 11.8.4, with links to detailed information on each push, see the .

Download Release Notes Changelog Overview of 11.8

^{Alternate download from mariadb.org}

Release date: 4 Jun 2025

MariaDB 11.8.2 is a Stable (GA) release. It is an evolution of MariaDB 11.7 with several entirely new features.

MariaDB 11.8 is a long-term release.

Thanks, and enjoy MariaDB!

Notable Items

Storage Engines

InnoDB

• Race condition between log_t::resize_start() and log_t::resize_abort() ()

• Race conditions between ALTER TABLE or OPTIMIZE TABLE and the purge of transaction history were fixed. ()

• Server crashes when resizing default innodb buffer pool after setting innodb-buffer-pool-chunk-size to 1M ()

• ASAN errors in dict_sys_t::load_table / get_foreign_key_info after failing to load a table ()

RocksDB

• Assertion `!level_and_file.second->being_compacted' failed in LevelCompactionBuilder::SetupInitialFiles ()

• Assertion `ikey_.type == kTypeValue' failed in rocksdb::CompactionIterator::NextFromInput ()

Spider

• 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. fixes this. ()

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

Connect

• Connect crashes server because of duplicate 'free()' in GetUser ()

Versioned Tables

• Assertion InnoDB searching row in wrong partition for multiple system versioned DELETE with same timestamp and same multistatement transaction ()

Optimizer

• A server crash is possible when a statement is executed that satisfies all of these requirements: ()

  • It is a data-modifying statement (UPDATE/DELETE/etc)

  • It uses a condition that produces a warning during optimization (typically, a type mismatch)

  • The client is using a bulk operation

Stored routines

• Stored routine with a cursor crashes on the second execution if a DDL statement happened ()

Data Definition - Alter Table

• ALTER TABLE…SEQUENCE does not work correctly with InnoDB ()

• The server could crash when an UPDATE is about to commit concurrently with a CREATE INDEX that includes VIRTUAL columns ()

• ALTER TABLE…DROP COLUMN after a failed ALTER TABLE…DROP COLUMN could lead to a server crash ()

Backup

• mariadb-backup --backup crash during innodb_undo_log_truncate=ON, innodb_encrypt_log=ON ()

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

• make mariadb-backup to force an innodb checkpoint ()

GIS

• Server aborts while deleting the record in spatial index ()

Upgrades

• Upgrades fail on Windows ()

Server

• MariDB 11.7.2 - /usr/sbin/mariadbd got signal 11 ()

• Protocol_text allocates memory without error checking, potentially leading to server crashes. ()

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

OTHER

• Field pointer may be uninitialized in fill_record ()

• Extend SBOM with 'license' and 'copyright' ()

• Wrong results from tables with a single record and an aggregate ()

Replication

• 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`). ()

• Semi-sync Replica Can't Kill Dump Thread When Using SSL ()

• CREATE-or-REPLACE-SELECT with ROW binlog format may not log DROP TABLE events, potentially causing replication issues. ()

• Mysqlbinlog --stop-position does not warn if EOF not reached with --read-from-remote-server (

Character Sets

• Assertion `src != ((void *)0)' failed in my_casedn_8bit ()

• The collation utf8mb4_0900_bin is defined as an alias for utf8mb4_bin while it should be an alias of utf8mb4_nopad_bin, causing wrong comparison results. ()

Authentication and Privilege System

• MariaDB crashes when trying to access information_schema.users when started with --skip-grant-tables ()

• User without any privileges to a sequence can read from it and modify it via column default ()

• User has unauthorized access to a sequence through a view with security invoker ()

Galera

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

Partitioning

• corruption when query cache cannot allocate block ()

Data Manipulation - Update

• Stack looping and SIGSEGV in Item_args::walk_args on UPDATE ()

Vector search

• Crash on disconnect when dropped Aria table with vector key under lock ()

• Support for powerpc64 SIMD instructions in the distance calculation function of the mhnsw algorithm is added. ()

Virtual Columns

• Server crashes when reading information_schema.COLUMNS after creating a table with virtual columns using the GIS data type ()

Plugin - Audit

• Long server_audit_file_path causes buffer overflow ()

Sequences

• Check when doing ALTER TABLE table_name sequence=1 that table can be a sequence ()

Data types

• Comparison ROW(stored_func(),1)=ROW(1,1) erroneously called stored_func() twice per row. It led to a performance degradation, as well as to a double execution of the possible stored function side effects. ()

Configuration

• Bad value for the variable "Buffer pool size" ()

• Get option group suffix from $MARIADB_GROUP_SUFFIX in addition to $MYSQL_GROUP_SUFFIX ()

• my_getopt compares option names case sensitively ()

Parser

• In sql_mode=ORACLE, package body variables are not allowed as FETCH targets ()

Locking

• Segfault on concurrent ALTER and SELECT for partitioned table ()

Packaging

• Error while installing MariaDB on Windows Server 2022 due to antivirus interference. ()

• Systemd: Restart on OOM ()

• RHEL 8 (and compatible) + Ubuntu 20.04 cannot start systemd servce (EXIT_CAPABILTIES/218) ()

• remove all RPM MariaDB-compat packages (with old shared libraries) ()

Scripts & Clients

• mariadb-dump used wrong quoting character ()

JSON

• JSON_UNQUOTE doesn't work with emojis ()

Prepared Statements

• mysql_stmt_errno() returns 0 after an error in mysql_stmt_execute() ()

Binary Protocol

• When a CREATE TABLE .. SELECT errors while inserting data, a user would expect that all changes are rolled back and the table would not exist after executing the query; however, the error was accidentally ignored in the code, and the table would still exist. ()

Changelog

For a complete list of changes made in MariaDB 11.8.2, with links to detailed information on each push, see the .

Contributors

For a full list of contributors to , see the .