Last checked and updated on 13 Jun 2026
What Is New in MariaDB 11.2
MariaDB 11.2 is a stable release that consolidates features from previous development series, focusing on enhancements to the optimizer, security, and compatibility. It's a solid upgrade for production systems looking for improved performance and stability.
| Category | Key Changes |
|---|---|
| New Features | System-versioned table comments, IGNORE BAD FILE option, new status variables. |
| Optimizer & Performance | Better hash join and subquery optimization, improved cost model. |
| Security | OpenSSL 3.0 support, deprecation of yaSSL and wolfSSL. |
| Deprecated & Removed | Deprecated system variables, removal of InnoDB system tables. |
| Bug Fixes | Numerous fixes across replication, storage engines, and the optimizer. |
What optimizer improvements were made?
The optimizer received significant tuning for better query execution out-of-the-box. Hash joins are now more efficient, and the cost-based model has been refined for more accurate planning.
Subquery optimizations reduce unnecessary overhead, which matters for complex analytical queries. These changes mean common queries should run faster without requiring manual hinting.
How does it handle security updates?
This release bumps OpenSSL support to version 3.0, which is a major step for maintaining modern cryptographic standards. The older yaSSL and wolfSSL libraries are now officially deprecated.
In practice, this pushes deployments towards a more standardized and maintained encryption stack. You'll want to ensure your OS provides a compatible OpenSSL package.
What new DBA features should I know about?
For DBAs, the IGNORE BAD FILE option for LOAD DATA is a welcome addition. It allows the statement to skip over malformed lines in a data file instead of failing entirely.
You can now also add comments to system-versioned tables, which helps with documenting temporal data schemas. New status variables like Handler_tmp_write and Handler_tmp_update provide better insight into temporary table operations.
Is anything being removed or deprecated?
Yes, several legacy features are on their way out. The innodb_undo_log_truncate and innodb_undo_directory variables are now deprecated. The old InnoDB system tables (INNODB_*) have been removed in favor of the INFORMATION_SCHEMA equivalents.
This cleanup reduces code complexity and pushes users towards more standard interfaces. Check your scripts for any references to these deprecated elements.
What about replication and storage engines?
The release includes various fixes to enhance replication robustness. Several bugs related to ALTER TABLE operations on tables with atomic DDL were squashed.
For storage engines, issues in MyRocks, ColumnStore, and Spider were addressed. These fixes improve overall stability for deployments using these engines.
FAQ
Should I upgrade to MariaDB 11.2 for the optimizer improvements alone?
If you're running complex queries with joins or subqueries, yes. The refined cost model and hash join optimizations can provide tangible performance gains without any application changes.
Is the move to OpenSSL 3.0 a breaking change?
It can be if your system relies on a deprecated OpenSSL 1.1.1. You need to ensure your operating system or environment provides OpenSSL 3.0 support before upgrading.
What happens if I use a deprecated variable like innodb_undo_directory?
It will still work for now but will generate a warning. You should plan to remove it from your configuration, as it will likely be removed in a future major release.
How does the IGNORE BAD FILE option work?
When added to a LOAD DATA INFILE statement, it instructs the server to log warnings for bad input lines but continue processing the rest of the file. This is much better than having the entire job fail.
Were there any fixes for Galera Cluster in this release?
This specific release note does not highlight Galera changes. For detailed Galera cluster updates, you should consult the corresponding Galera release notes that are compatible with MariaDB 11.2.