This section contains release notes for MariaDB Server releases divided into the major MariaDB series. The latest long-term stable series is MariaDB 11.8 (maintained for three years), the current rolling release is MariaDB 12.1, and the current development releases are MariaDB 12.2 and MariaDB 12.3.

_{This page is licensed: CC BY-SA / Gnu FDL}

The MariaDB development release policy has the following project commitments for the maturity stages:

Commitment for Alpha Releases

New features are being added. Some old features may be removed. Users can start trying Alpha versions out, but should not expect feature stability yet. Still, should show no regressions and should have no open level bugs for this release.

Commitment for Beta Releases

Features can not be removed anymore. Users can start building applications using MariaDB Beta releases. Any application that works with MariaDB Beta release will continue to work with a RC and GA release. The syntax that was valid in Beta will stay valid, tables created in Beta will stay readable, Beta clients will be able to connect to GA servers, and so on.

Commitment for Gamma/RC Releases

The server is feature complete. No new features, no changes in default settings are possible. From this point only bug fixes are accepted into the server.

Commitment for Stable/GA Releases

We believe the code is ready for general usage (based on bug inflow).

Plugins

Plugins generally follow the same rules, but they have . That is, a plugin is declared Gamma when it becomes feature complete. This happens independently from the server being Alpha, Beta, RC, or GA.

Security Releases

See our page for information of how and when emergency security releases are done.

_{This page is licensed: CC BY-SA / Gnu FDL}

The MariaDB project is a community project governed by the MariaDB Foundation. Please see the Maintenance Policy on the MariaDB Foundation website.

The MariaDB project is as active as the community around it and the MariaDB Foundation members actively working on and enhancing MariaDB. Therefore, from the MariaDB project perspective, the aspiration is for each major version of MariaDB to be maintained for quite a while after its initial stable (GA) version. For specific dates related to each version and more details, see the MariaDB Deprecation Policy. You may also want to review the MariaDB plc Engineering Policies.

Additional Technical Support

MariaDB plc can of course offer additional Technical Support and Services to their customers that cover the versions even longer and provide SLA commitments for additional feeds. Please for more details.

_{This page is licensed: CC BY-SA / Gnu FDL}

SET SQL_MODE=MSSQL implies all the following flags:

From time to time some features in MariaDB will be marked something as deprecated. This is done to warn MariaDB users that the feature is likely to disappear in some upcoming major version and give them time to adapt to the change.

The policy is that "It is unacceptable for a user to upgrade from a supported version A where a feature works normally to a version B where a feature doesn't exist without an advanced warning."

Thus, when a feature is removed for some reason, the sequence of steps is as follows:

1. the feature is marked as deprecated.

2. we wait until all releases where the feature is not deprecated have reached EOL.

3. now the feature can be removed in the next major version before GA. It will not be removed in a minor update!

With an LTS lifetime of 5 years, step 2 normally means that a feature cannot be removed until it's marked deprecated for 5 years.

Typical things that are deprecated:

• Variables, options or status variables that have lost their meaning or have been renamed.

• Features/behavior that have been replaced with better functionality.

• Features that conflicts with the SQL standard.

We do our best to ensure that upgrading to a new major version of MariaDB is as smooth and uneventful as possible. This means that we go to great lengths to keep things compatibility, even when removing deprecated features:

• MariaDB server will keep old startup variables around even after they are removed (deprecation has taken effect). Assigning a value to a removed variable will produce a warning in the error log.

• Some removed features/behavior that we know is still important for some users, we still keep available behind a dedicated option, which will give it at least 5 more years until disappearance.

_{This page is licensed: CC BY-SA / Gnu FDL}

This is an overview of query optimizer feature development in recent versions of MariaDB (5.5, 10.0) and MySQL (5.6).

To make things easier to understand, let's first partition the optimizer into areas:

Let's look at things in historical order. There is no known evidence of the use of SQL query optimization by ancient Egyptians. In April 2012, and became stable. (5.5 was a merge of 5.3 with MySQL 5.5). The 5.3/5.5 release included a number of major new query optimizer features:

The size of the bubble roughly corresponds to the impact of the feature (in the opinion of the author of this article). "Hash join" is in quotes, because is not what is generally meant by hash join in the world of databases. Smaller features and bug fixes are not shown.

Current Release Model (from MariaDB 11.3)

• MariaDB Community Server releases happen four times a year.

• There is a new innovation release with new features every time. It is a Release Candidate (RC) release.

• Additionally, all maintained release series get a new patch version maintenance release, a release that was RC last time, becomes Generally Available (GA).

• There are no patch version releases of an innovation release after GA (except for emergency releases), instead users are supposed to upgrade to the next minor innovation release. In other words, innovation releases are rolling releases, one upgrades 11.3.2→11.4.2→11.5.2→11.6.2→11.7.2

• Approximately every fourth innovation release is a long-term support (LTS) release, after the GA release, with additional Enterprise and Extended support available.

• Between two innovation releases there is a preview, it is feature-complete, but has alpha maturity, its purpose is to showcase new upcoming features. Every feature that will be in a release must have been in a preview at some point

• The opposite is not true, the feature from a preview will not necessarily be in the upcoming RC innovation release — this depends on whether the feature itself can be considered RC. If it isn't stable enough, it'll stay on internal testing and bug fixing until it is ready.

The release schedule looks about the same every year:

• Every third month there's a new minor innovation release, and a new patch version for the previous innovation release to bring it to GA, and also a patch version for currently maintained LTS releases:

  • early February, early May, early August, early November

• Previews happen between innovation releases:

References:

Historical Release Models

From to

Almost the same as above, except that

• An innovation release is maintained for one year after its first GA release (see, for example, ), they are not rolling, but on short-term support.

• Approximately every eighth innovation release (+-1, aligned around Debian release schedules) is a long-term support (LTS) release, maintained for five years after its first GA release.

• An LTS release concludes a major release series, the next innovation release will have a new major version number

From to

• There is a new release series every year

• It's maintained for five years after the first GA release

• A release is going through conventional alpha, beta, RC maturity phases until reaching GA

From to

• It is a feature based model

• A new release series is planned to have a specific set of features

• It is released when they are ready

_{This page is licensed: CC BY-SA / Gnu FDL}

MariaDB 12.3 is a , maintained until June 2029.

New Features

Compatibility Features

• Oracle TO_DATE() function ()

• Support for cursors on prepared statements ()

• SQL Standard SET PATH statement ()

Replication

• Configurable defaults for MASTER_SSL_* settings for CHANGE MASTER ()

• Fragment ROW replication events larger than max_packet_size ()

Miscellaneous

• Hashicorp Plugin: Implement cache flush for forced key rotation ()

• New hash algorithms for PARTITION BY KEY ()

• Optimise reorderable LEFT JOINs ()

Notable Items

Galera

• The Galera package dependency has been removed from server packages and the Galera package is no longer included in the MariaDB repositories ()

List of All MariaDB 12.3 Releases

_{This page is licensed: CC BY-SA / Gnu FDL}

Release date: 21 Nov 2025

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

MariaDB 12.2.1 is a release.

Thanks, and enjoy MariaDB!

New Features

Compatibility features

• : [NO_]ROWID_FILTER (),

• : [NO_]INDEX_MERGE ()

• : Implicit query block names ()

Miscellaneous

• Remove depth limit of 32 from JSON functions ()

• Indexes on derived tables with GROUP BY produce wrong out_rows estimates ()

• Add ()

Changelog

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

_{This page is licensed: CC BY-SA / Gnu FDL}

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

New Features

Compatibility features

• Implement Oracle function ()

• Implement Oracle function ()

Optimizer

• Join optimizer is now able to infer that derived table with GROUP BY clause has distinct GROUP BY columns ()

Optimizer hints

• : [NO_]ROWID_FILTER (),

• : [NO_]INDEX_MERGE ()

• : Implicit query block names ()

Miscellaneous

• Remove depth limit of 32 from JSON functions ()

• Add ()

• Implement .PARAMETER_DEFAULT column ()

Preview release only

These features needed further testing and will be implemented in a future series.

• Implement Global temporary tables () (preview release only)

• Improved support of between tables of different structure () (preview release only)

List of All MariaDB 12.2 Releases

_{This page is licensed: CC BY-SA / Gnu FDL}

Download Release Notes Changelog Overview of 12.3

Release date: 12 Feb 2026

MariaDB 12.3 is a long term release, maintained until June 2029. It is an evolution of MariaDB 12.2 with several entirely new features.

MariaDB 12.3.1 is a release.

Thanks, and enjoy MariaDB!

New Features

Compatibility Features

• Oracle TO_DATE() function ()

• Support for cursors on prepared statements ()

• SQL Standard SET PATH statement ()

Replication

• Configurable defaults for MASTER_SSL_* settings for CHANGE MASTER ()

• Fragment ROW replication events larger than max_packet_size ()

Miscellaneous

• Hashicorp Plugin: Implement cache flush for forced key rotation ()

• New hash algorithms for PARTITION BY KEY ()

• Optimize reorderable LEFT JOIN statements ()

Notable Items

Galera

• The Galera package dependency has been removed from server packages and the Galera package is no longer included in the MariaDB repositories ()

Data Definition - Create Table

• On an error in CREATE TEMPORARY TABLE ... SELECT, InnoDB internally aborted a transaction, while the server thought the transaction still existed. This caused various inconsistencies in the binary log, disappearing savepoints, and more. The issue was fixed differently in different versions. In 10.11.16, 11.4.10, 11.8.6, and 12.2.2, the transaction is consistently and completely rolled back if CREATE TEMPORARY TABLE ... SELECT fails with an error. In 12.3.1, there is no rollback at all. ()

Changelog

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

_{This page is licensed: CC BY-SA / Gnu FDL}

This page describes replication compatibility between MariaDB and MySQL. For replication compatibility details between different MariaDB versions, see .

Replication Compatibility

compatibility depends on:

The following is a list of all function differences between and MySQL 5.7. It is based on functions available in the stable versions MySQL 5.7.18 and .

For a description of all differences, see .

Present in MariaDB Only

Release date: 12 Feb 2026

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

MariaDB 12.2.2 is a release.

The following is a list of all function differences between MariaDB 10.3 and MySQL 5.7. It is based on functions available in the stable versions MySQL 5.7.18 and MariaDB 10.3.29.

For a description of all differences, see Incompatibilities and Feature Differences Between MariaDB 10.3 and MySQL 5.7.

Present in MariaDB Only

Dynamic Columns

General

JSON

Regular Expressions

Sequences

Window Functions

Present in MySQL Only

GTID

MariaDB and MySQL have differing implementations.

• GTID_SUBSET

• GTID_SUBTRACT

• WAIT_FOR_EXECUTED_GTID_SET

• WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS()

Geographic

• DISTANCE

• MBRCOVEREDBY

• ST_BUFFER_STRATEGY

• ST_GeoHash

Miscellaneous

• ANY_VALUE

• RANDOM_BYTES

• RELEASE_ALL_LOCKS

• VALIDATE_PASSWORD_STRENGTH

See Also

The following is a list of all function differences between MariaDB 10.2 and MySQL 5.6. It is based on functions available in the stable version MariaDB 10.2.25.

Present in MariaDB Only

Dynamic Columns

JSON

Regular Expressions

Window Functions

Present in MySQL Only

GTID

MariaDB and MySQL have differing implementations.

• GTID_SUBSET

• GTID_SUBTRACT

• SQL_THREAD_WAIT_AFTER_GTIDS()

• WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS()

Miscellaneous

• RANDOM_BYTES

• VALIDATE_PASSWORD_STRENGTH

See Also

Release date: 18 Nov 2025

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

MariaDB 12.1.2 is a release.

Download Release Notes Changelog Overview of 12.0

^{Alternate download from mariadb.org}

Release date: 7 Aug 2025

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

MariaDB 12.0 is a rolling release. One is expected to upgrade to MariaDB 12.1.2, there will be no 12.0.3.

Thanks, and enjoy MariaDB!

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

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

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

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

_{This page is licensed: CC BY-SA / Gnu FDL}

The below is a table view. For a more graphical view of the differences see .