Last checked and updated on 10 Jun 2026
What Is New in MariaDB 11.1
MariaDB 11.1 is a stable (GA) release that introduces significant new features, performance improvements, and important bug fixes. This version focuses on enhancing the optimizer, expanding SQL standard support, and improving overall system reliability.
| Category | Key Changes |
|---|---|
| New Features | Generated columns, CHECK constraints, SQL/JSON constructors, System-versioned tables |
| Improvements | Optimizer enhancements, Prepared statement caching, Faster privilege checking |
| Security | OpenSSL 3.0 support, Authentication improvements |
| Deprecations & Removals | Deprecated system variables, Removal of InnoDB system tables |
| Bug Fixes | Numerous fixes for replication, storage engines, and crashes |
What are the major SQL feature additions?
MariaDB 11.1 brings the database closer to full SQL standard compliance with several key features. Generated columns allow you to define columns whose values are computed from expressions involving other columns. This is useful for simplifying queries and ensuring data consistency.
CHECK constraints are now fully supported, enabling you to enforce domain integrity directly at the database level. The release also introduces SQL/JSON constructor functions (JSON_ARRAY(), JSON_OBJECT()) and system-versioned tables for built-in temporal data tracking.
How does the optimizer get better in 11.1?
The optimizer receives substantial upgrades aimed at generating more efficient query execution plans. A new cost model for the range optimizer improves its decision-making process when choosing indexes. The introduction of prepared statement caching for bulk inserts significantly boosts the performance of repeated insert operations.
Faster privilege checking reduces overhead during query execution, which matters most in environments with complex user permission structures. These changes collectively mean that many workloads will see a noticeable reduction in query latency without any application code changes.
What security updates should I be aware of?
This release adds support for OpenSSL 3.0, ensuring compatibility with the latest security libraries and algorithms. The authentication process has been improved, particularly for the mysql_native_password plugin, making it more robust.
While not a direct security feature, the deprecation of the innodb_undo_log_truncate variable and the removal of old InnoDB system tables help streamline the configuration and reduce the potential attack surface of the database.
What has been deprecated or removed?
MariaDB 11.1 continues the cleanup of legacy features. The system variables innodb_undo_log_truncate and innodb_undo_tablespaces are now deprecated. The old InnoDB system tables (INNODB_*) have been completely removed; you should use the corresponding INFORMATION_SCHEMA tables instead.
This cleanup is part of a long-term effort to simplify the codebase and maintenance. In practice, you should audit your scripts and configuration files for any references to these deprecated elements to ensure a smooth upgrade path.
Which bug fixes are most critical?
The release notes list numerous fixes, but a few stand out for their impact on stability. Critical fixes address crashes that could occur under specific conditions in stored routines and with the JSON_TABLE function. Replication reliability is improved with fixes for issues that could cause a replica to stop.
Other important fixes resolve problems with storage engines, including InnoDB and MyRocks, and correct the behavior of various SQL functions and the optimizer. These fixes collectively enhance the overall robustness of the database server for production use.
FAQ
Are generated columns stored on disk or computed on the fly?
MariaDB 11.1 supports both virtual (computed on read) and persistent (stored on disk) generated columns. You define this using the VIRTUAL or PERSISTENT keywords in the column definition.
Does the new prepared statement cache work with all connectors?
The bulk insert prepared statement cache is a server-side improvement. It should benefit any client that performs repeated bulk insert operations, regardless of the connector used, as it reduces the server's parsing overhead.
What replaces the removed InnoDB system tables?
The old INNODB_* tables have been replaced by their counterparts in the INFORMATION_SCHEMA. For example, you should now query INFORMATION_SCHEMA.INNODB_TABLES instead of the old INNODB_SYS_TABLES table.
Is OpenSSL 3.0 now a requirement for MariaDB 11.1?
No, OpenSSL 3.0 is not a requirement. MariaDB 11.1 adds support for it, meaning you can compile and run the server against OpenSSL 3.0 libraries. It remains compatible with older supported versions of OpenSSL and other SSL libraries.
How do CHECK constraints interact with existing applications?
Existing tables will not have CHECK constraints automatically added. You must alter your tables to add them. The database will then enforce the constraint for all new INSERT and UPDATE operations, which could cause errors for applications that violate the new data rules.