MariaDB 11.4 is a current long-term series, maintained until May 2029.

Upgrading

• See and .

New Features

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

Optimizer

• Major improvements to the Optimizer. See .

• for single-table / statements. Update and delete statements that use subqueries can now use all subquery optimization strategies that MariaDB offers, so now if you use subqueries in UPDATE or DELETE, these statements will likely be much faster (, )

• Queries with the or functions comparing against a constant can now make use of indexes, so these will be noticeably quicker in certain instances. For example SELECT * FROM t2 WHERE YEAR(a) = 2019 or SELECT * FROM t2 WHERE DATE(a) <= '2017-01-01'

InnoDB

• Shrink without restart by setting the system variable. (, )

• The is now shrunk by reclaiming unused space at startup (, )

Online Schema Change

• can now do most operations with ALGORITHM=COPY, LOCK=NONE, that is, in most cases, unless the algorithm and lock level are explicitly specified, ALTER TABLE will be performed using the algorithm while simultaneously allowing concurrent on the altered table. ()

For more information, refer to, .

Replication and Binary Log

• writing speed was improved by moving checksum calculations out of the global binlog mutex (). The system variable is available if the old behavior is desired. This is a contribution by Kristian Nielsen

• New system variable enables binary log purging when the total size of all binary logs exceeds the specified threshold. The implementation is based on the patch from Percona ()

• New system variable disables binary log purging until the number of connected slaves reaches the specified threshold ().

SSL/TLS

• is now enabled in the server by default. No configuration necessary, if no server certificate was provided a self-signed certificate will be automatically generated by the server. See for details ().

• Clients now can validate self-signed server certificates if the or authentication is used and account password is not empty ().

• Clients now require SSL and have enabled by default ().

JSON

• now allows retrieval of the key when iterating on JSON objects (, )

• New functions , and to check for JSON intersection (, )

• extracts key/value pairs from a JSON object (, )

Data Types

• It is now possible to create on tables that contain (, )

• data types can now be cast into types (, )

• This means INET4 values can be compared with INET6 values and can be inserted into INET6 columns; the server can automatically convert INET4 value into INET6 as needed ()

Backup and Restore

• New option, -j, --parallel= for increased parallelism, specifies the number of dump table jobs executed in parallel (only for use with the --tab option). Also added to , with --use-threads as a synonym. ()

• mode has been deprecated (, )

Application-Time Periods

• Add views for in information_schema (), in particular

• New view

• New view

• New columns IS_SYSTEM_TIME_PERIOD_START and IS_SYSTEM_TIME_PERIOD_END

Sys Schema

• New view shows granted privileges broken down by table on which they allow access and level on which they were granted. For example, if a user x has SELECT privilege granted ON db.*, this view will list all tables in the db schema with the user x having SELECT privilege on them. This is different from , which only lists privileges granted on the table level ()

Partitioning

• and now support the WITH VALIDATION and WITHOUT VALIDATION clauses. If neither is specified, the default behavior is WITH VALIDATION ()

Collations

From :

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

Connection Redirection

• Added a using the system variable (, )

• At the moment client-side support is missing

Privileges

• Add a new database-level , SHOW CREATE ROUTINE that allows one to see the routine definition even if the user isn't the routine owner (, )

Spider

• The preferred way to specify is to use the dedicated Spider table options (implemented in ). Abusing the table COMMENT clause is now deprecated ()

• The storage engine now supports table options instead of having to encode them in COMMENT/CONNECTION strings. When any table option is specified, Spider will ignore COMMENT/CONNECTION strings at the same table/partition/subpartition. A new variable is introduced to ignore them globally at all levels (table/partition/subpartition). Another variable, , is introduced to suppress warnings when Spider ignores COMMENT/CONNECTION strings. (, )

Miscellaneous Functions

• function now supports conversion up to base 62 ()

• Values generated by the Key Derivation Function are resistant against password hashing generators, so are good for strongly hashed passwords ()

• Given a time in picoseconds, the new function returns a human-readable time value and unit indicator (, )

Date and Time

• function can now print the current time zone abbreviation and current time zone offset from UTC with %Z and %z format specifiers. (, )

Processlist

• Added a SENT_ROWS column to the table, as well as extended the display size for the columns in processlist to ensure that most results will fit in display (, )

Miscellaneous

• Added support for packages () outside of ()

• Setting a non-default value will now always issue a deprecation warning (, )

• enhancement (, )

• Temporary tables are now displayed in the ,

Variables

• For a list of all new variables, see .

Removed

• Remove thr_alarm from server codebase

  • Includes removal of the system variable ()

• In addition, the following deprecated features and system variables have been removed (, ):

Security Vulnerabilities Fixed in

For a complete list of security vulnerabilities (CVEs) fixed across all versions of MariaDB, see the page.

• :

• :

List of All Releases

Download Release Notes Changelog Overview of 11.4

Release date: 8 Aug 2024

MariaDB 11.4 is the current long-term series of MariaDB and will be maintained until May 2029. It is an evolution of MariaDB 11.3 with several entirely new features.

MariaDB 11.4.3 is a Stable (GA) release.

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

Thanks, and enjoy MariaDB!

Notable Items

Storage Engines

InnoDB

• now builds indexes more efficiently ()

  • Unsetting the system variable restores the old behavior.

• Fix unexpected storage read IO for the redo log, reintroduce ()

• Correctly terminate transaction early with ER_LOCK_TABLE_FULL when lock memory is growing (

Aria

• Fix index corruption when doing a REPAIR TABLE that has a size of over 4G ()

Spider

• UBSAN: runtime error: applying non-zero offset in spider_free_mem and SIGSEGV in spider_free_mem on SELECT ()

• SIGSEGV in ha_resolve_storage_engine_name, UBSAN: runtime error: index 4294967295 out of bounds for type 'st_plugin_int *[64]' ()

• SIGSEGV in spider_db_conn::fin_loop_check, and ASAN: heap-use-after-free in

Partitioning

• SIGSEGV in parse_engine_part_options on INSERT, SELECT or ALTER ()

• Assertion ``auto_increment_value'failed inha_partition::info` on INSERT into MEMORY table ()

Character Sets

• On startup: UBSAN: applying zero offset to null pointer in my_copy_fix_mb from strings/ctype-mb.c and other locations ()

• On startup: UBSAN: runtime error: applying zero offset to null pointer in skip_trailing_space and my_hash_sort_utf8mb3_general1400_nopad_as_ci ()

• SHOW CREATE DATABASE statement crashes the server when db name contains some unicode characters, ASAN stack-buffer-overflow (

Optimizer

• On startup: UBSAN: runtime error: applying non-zero offset in JOIN::make_aggr_tables_info in sql/sql_select.cc ()

• Crash after killing query while it is processed by test_quick_select ()

• Extend condition normalization to include 'NOT a' ()

• Auto-generated from table no longer breaks replication ()

• Fix replication failure when are used where the replica has set and the client has touched a different database when running DML such as inserts. ()

• Fix replication error when is used in conjunction with a password longer than 41 ascii characters ()

Backup

• Hide password passed on commandline from xtrabackup_info ()

Galera

• updated to 26.4.19

  • NOTE: Includes increasing the GCS protocol version, which prevents downgrades of individual nodes in the cluster as soon as all nodes have been updated

• galera_gtid_2_cluster: Assertion ``thd->wsrep_next_trx_id() != (0x7fffffffffffffffLL * 2ULL + 1)'` ()

Error Log

• system variable added, and value added to the at startup ()

General

• As per the , this will be the last release of for Debian 10 "Buster", RHEL/CentOS 7, Ubuntu 23.10 "Mantic", and Fedora 38

• Repositories for Ubuntu 24.04 "Noble" have been added

• no longer unnecessarily traverses tablespaces list ()

• Fix unknown variable defaults-group-suffix=

Changelog

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

Contributors

For a full list of contributors to , see the .

Download Release Notes Changelog Overview of 11.4

Alternate download from mariadb.org

Release date: 22 May 2025

MariaDB 11.4 is the current long-term series of MariaDB and will be maintained until May 2029. It is an evolution of MariaDB 11.3 with several entirely new features.

MariaDB 11.4.7 is a Stable (GA) release.

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

Thanks, and enjoy MariaDB!

Notable Items

Storage Engines

• Huge performance drop after update ()

• InnoDB buffer pool reserves all assigned memory even with no/minimum load ()

• Possible data loss in the unlikely scenario when GET GLOBAL innodb_buffer_pool_size is shrinking the size of the buffer pool while the buffer pool contains ROW_FORMAT=COMPRESSED tables that use a non-default KEY_BLOCK_SIZE that is equal to innodb_page_size/1024 ()

Optimizer

• Optimizer trace should show the index name in the block chosen_access_method ()

Server

• Make HOSTNAME a cmake configure variable ()

General

• As per the , this will be the last release of for Ubuntu 20.04 LTS 'focal'

Changelog

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

Release date: 24 December 2023

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

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

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

For an overview of see the page.

Thanks, and enjoy MariaDB!

Download Release Notes Changelog Overview of 11.4

Release date: 1 Nov 2024

MariaDB 11.4 is the current long-term series of MariaDB and will be maintained until May 2029. It is an evolution of MariaDB 11.3 with several entirely new features.

MariaDB 11.4.4 is a Stable (GA) release.

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

Thanks, and enjoy MariaDB!

Notable Items

Storage Engines

InnoDB

• Fix attempt to read outside the bounds of the file: ./ibdata1 ()

• Fix MariaDB crash with SIGILL because the OS does not support AVX512 ()

• Fix deadlock caused by lock_rec_unlock_unmodified() ()

• Fix duplicate key error in table 'mysql.innodb_table_stats' ()

• Fix server crash when calling after is enabled ()

• SELECT MIN on Spider table no longer returns more rows than expected ()

• Fix Spider group by handler wrong result on order by aggregate ()

• Fix Storage Engine S3 that caused 500 error when using Huawai Cloud S3 and possibly other S3 providers ()

  • A new option has been added. s3-provider=Huawai needs to be set for Huawai Cloud S3

  • New option , if true, SSL certificate verification for the S3 endpoint is disabled

Optimizer

• Fix crash caused by query containing constant having clause ()

• Fix assertion with optimizer_join_limit_pref_ratio and 1-table select ()

Data Definition - Alter Table

• Fix InnoDB crash under Windows Subsystem for Linux on ALTER TABLE or OPTIMIZE TABLE ()

• Modification of the column now correctly checks foreign key constraint ()

• Fix incorrect NULL value handling for instantly dropped BLOB columns ()

• Galera updated to 26.4.20

• Fix server crash when setting wsrep_cluster_address after adding invalid value to wsrep_allowlist table ()

• TOI (ALTER) no longer hangs on a parent table if SR transaction is in progress on a child table ()

• Fix INSERT...SELECT' on MyISAM table suddenly replicated by alera ()

Backup

• Recovery now correctly notes some log corruption ()

• InnoDB now correctly merges the change buffer to ROW_FORMAT=COMPRESSED tables ()

• Can now selectively restore sequences using innodb tables from backup ()

JSON

• now properly unquotes strings ()

• default values now allows non-string literals ()

General

• As per the , this will be the last release of for Windows 11 22H2

• no longer hangs on startup when --init-file target does not exist ()

• LOAD DATA INFILE with geometry data no longer fails ()

• Fix heap-use-after-free in group_concat with compressed or GIS columns ()

Security

• Fixes for the following :

  • CVE-`-```

Changelog

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

Contributors

For a full list of contributors to , see the .

Download Release Notes Changelog Overview of 11.4

^{Alternate download from mariadb.org}

Release date: 6 Aug 2025

MariaDB 11.4 is the current long-term series of MariaDB and will be maintained until May 2029. It is an evolution of MariaDB 11.3 with several entirely new features.

MariaDB 11.4.8 is a Stable (GA) release.

Thanks, and enjoy MariaDB!

Notable Items

Storage Engines

InnoDB

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

  • After a failed shrinking of innodb_buffer_pool_size, the adaptive hash index will not be re-enabled if innodb_adaptive_hash_index was ON when SET GLOBAL innodb_buffer_pool_size=... started to execute. (

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

Data Definition - Create Table

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

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

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

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

Character Sets

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

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.4.8, with links to detailed information on each push, see the .

Note: This page describes features in the source repository for MariaDB 11.4. There are currently no official packages or binaries available for download which contain the features. If you want to try out any of the new features described here you will need to and the code yourself.

Release Notes Changelog Overview of 11.4

MariaDB 11.4 is the current long-term series of MariaDB and will be maintained until May 2029. It is an evolution of MariaDB 11.3 with several entirely new features.

MariaDB 11.4.6 is a Stable (GA) release.

For an overview of MariaDB 11.4 see theWhat is MariaDB 11.4? page.

Thanks, and enjoy MariaDB!

Notable Items

Storage Engines

InnoDB

• Incorrect undo logging for indexes on virtual columns whose index ID does not fit in 32 bits ()

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

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

• CREATE INDEX fails to heal a FOREIGN KEY constraint ()

Spider

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

Optimizer

• group by handler missing constant fields when selecting from a view ()

• A multi-table UPDATE ... ORDER BY ... LIMIT statement could update the wrong rows when the ORDER BY clause was resolved by using temporary and filesort. ()

• A query using a subquery in form:

could cause a crash in the optimizer. The essential part is that ON expression has only two kinds of references: 1.to inner side of the outer join and 2. to outside the subquery. ()

• find_order_in_list mismatch when order item needs fixing() ()

• If the join_condition is specified via USING (column_list), the query plan depends on the sequence of tables in the query ()

• Large N-way OR causes a lot of index_merge variants to be created and discarded ()

• Wrong result in loose index scan ()

Data Definition - Alter Table

• Incorrect error handling on DDL with FULLTEXT INDEX ()

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

OTHER

• Field pointer may be uninitialized in fill_record ()

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

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

Server

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

Replication

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

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

Plugin - Audit

• Long server_audit_file_path causes buffer overflow ()

Configuration

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

Packaging

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

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

JSON

• JSON_UNQUOTE doesn't work with emojis ()

Security

• Fixes for the following :

Changelog

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

Release date: 4 Feb 2025

is the current long-term series of MariaDB and will be maintained until May 2029. 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.4

^{Alternate download from mariadb.org}

Release date: 6 Nov 2025

MariaDB 11.4 is the current long-term series of MariaDB and will be maintained until May 2029. It is an evolution of MariaDB 11.3 with several entirely new features.

MariaDB 11.4.9 is a Stable (GA) release.

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

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

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 MDEV-9804 "Implement a caching_sha2_password plugin" to MariaDB Community Server 11.4/11.8 ()

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

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

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.4.9, with links to detailed information on each push, see the .

Download Release Notes Changelog Overview of 11.4

Release date: 29 May 2024

MariaDB 11.4 is the current long-term series of MariaDB and will be maintained until May 2029. It is an evolution of MariaDB 11.3 with several entirely new features.

MariaDB 11.4.2 is a Stable (GA) release.

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

Thanks, and enjoy MariaDB!

Notable Items

From this version, the tool adds a new command to the top of every dump file. This command cannot be interpreted by MariaDB command line client versions that do not have the sandbox command, or by MySQL command line clients, and an error will be generated in these clients. Other methods of importing the dump will work not have this issue.

Storage Engines

InnoDB

• Introduce the system variable to address excessive context switching caused by log_sys.lsn_lock (observed on write-intensive workloads on NUMA systems) ()

• Fix InnoDB holding shared dict_sys.latch while waiting for FOREIGN KEY child table lock on DDL ()

• Fix adaptive hash index corruption after ()

• Server no longer aborts while altering an InnoDB statistics table ()

• Fixed that internal temporary tables did not wait for freed disk space, and related issues ()

• Fix wrong result on 2nd execution of prepared statement for query with derived table ()

• Server crashes when deleting partitions from a table with spider engine ()

• SPIDER plugin initialization failed at 'create table if not exists mysql.spider_tables ... with 'Specified key was too long; max key length is 1000 bytes', Warning: Memory not freed: 10720 ()

• spider plugin init failure with no_zero_date sql_mode ()

• sql plugin init failure with traditional sql_mode ()

Backup

• Port backup features from Enterprise Server. This adds support for to , and obsoletes the and options ()

• now preserves ()

• Fix problem on older mariadb (opendir(NULL)) caused by ()

,

• Fixed improper application of COLLATE to non-character columns ()

• Default charset now works with PHP MySQLi extension ()

• Fixed Bad SEPARATOR value in on character set conversion ()

• Fixed out of range error in (()) due to a wrong data type ()

JSON

• View created via now returns correct json object ()

• now detects the type of String Values and correctly returns Date/DateTime values ()

• no longer returns NULL on valid arguments ()

• no longer returns multiple values for same path ()

Encryption, TLS, SSL

• WolfSSL's math is unnecessarily slow ()

• Self-signed certificates are x509 Version 1, which are rejected by some TLS libraries ()

Optimization & Tuning

• Server crashes in JOIN_CACHE::write_record_data upon EXPLAIN with subqueries and constant tables ()

• Wrong result with cross Join given join order ()

• Wrong warnings on 2-nd execution of PS for query with GROUP_CONCAT ()

• Wrong result with semi-join and splittable derived table ()

Plugins

• The now reports the user and host in all cases ()

Replication

• --gtid-ignore-duplicate can double-apply event in case of parallel replication retry ()

• Deadlock kill of XA PREPARE can break replication / rpl.rpl_parallel_multi_domain_xa sporadic failure ()

• mysql_manager_submit Segfault at Startup Still Possible During Recovery ()

• Server crash in Rows_log_event::update_sequence upon replaying binary log ()

Galera

• updated to 26.4.18

  • NOTE: Includes increasing the GCS protocol version, which prevents downgrades of individual nodes in the cluster as soon as all nodes have been updated

• Disallow bulk insert operation during partition update statement ()

SQL, Data Definition, and Data Manipulation

• Transportable Tablespaces no longer leave in a mismatched state ()

• Fix wrong row targeted with "insert ... on duplicate" and "replace", leading to data corruption ()

• Fix incorrect DEFAULT expression evaluated in ()

• Fix server crash when UPDATE statement with duplicate key is run after setting a low thread_stack ()

Platforms & Packaging

• MariaDB-client community can't be installed in red hat ubi9 ()

General

Scripts & Clients

• It's now possible to disable system commands with the option. ()

• now exports the data with sandbox mode enable, so that the mariadb client will not execute potentially dangerous cli commands.()

• commands such as mariadb-dump --dump-slave=2 --master-data=2 now record both positions ()

Server

• Moving from to 10.6 mysql_upgrade is not updating some system tables ()

• Original IP not shown in network related error messages when proxy_protocol is in use ()

• Server incorrectly describes known variables as UNKNOWN if invalid values are specified at startup ()

• update case insensitive (large) unique key with insensitive change of value - duplicate key ()

Security

• Fixes for the following :

Changelog

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

Contributors

For a full list of contributors to , see the .

Release date: 16 Feb 2024

Do not use non-stable (non-GA) releases in production!

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!