Last checked and updated on 06 Jun 2026
What Is New in MariaDB 11.6
MariaDB 11.6 is a community release packed with enhancements that improve performance, add new functionality, and refine existing features. This version delivers tangible upgrades for developers and DBAs working with modern applications.
| Category | Key Changes |
|---|---|
| New Features | Generated Columns, System Versioning, CHECK Constraints, New Functions |
| Performance | InnoDB Optimizations, Parallel Replication, Query Optimizer Improvements |
| Security | Password Validation Plugin, OpenSSL 3.0 Support |
| SQL & Syntax | Extended JSON Support, New SQL Modes, ALTER TABLE Enhancements |
| Deprecated & Removed | Deprecation of InnoDB Monitors, Removal of Old Features |
What are the major new SQL features?
Generated columns and system-versioned tables are the headline SQL additions. Generated columns let you automatically populate a column's value using an expression based on other columns, which is fantastic for simplifying queries. System versioning brings native support for tracking the full history of row changes directly in the database.
CHECK constraints are another big win for data integrity. You can now enforce custom conditions on your data at the database level, preventing invalid data from being inserted in the first place. This is a long-awaited feature that brings MariaDB closer to other major SQL implementations.
How does performance get better in 11.6?
InnoDB sees significant optimizations, especially for high-concurrency write workloads. The internal locking mechanisms were improved to reduce contention, which means your applications can push more transactions per second without getting bogged down.
Parallel replication is now smarter and more efficient. Slaves can apply transactions from the relay log much faster, drastically cutting down on replication lag. For complex analytical queries, the optimizer has new tricks to choose better execution plans, making your reports run quicker.
What security enhancements were introduced?
The simple_password_check plugin is a straightforward but effective tool. It enforces basic password policies like minimum length and prevents the use of common, weak passwords right at the moment of user creation.
Under the hood, support for OpenSSL 3.0 is a critical update. It ensures the database can use the latest cryptographic libraries, which is essential for maintaining secure connections and staying current with security standards.
What's new for JSON and developer ergonomics?
JSON functionality gets a boost with new functions like JSON_TABLE, which allows you to transform JSON data into a standard table format that can be queried with regular SQL. This makes working with semi-structured data stored in JSON columns much more powerful.
Several other convenience features were added, such as the RANDOM_BYTES function for generating cryptographically secure random data. These small additions save developers from having to implement such logic in application code.
What has been deprecated or removed?
The InnoDB monitor tables in INFORMATION_SCHEMA are officially deprecated. The preferred method for getting this diagnostic information is now using Performance Schema tables, which offer a more standardized and efficient interface.
A few older and unused features were completely removed to clean up the codebase. This reduces maintenance overhead and potential security surface area, making the database more streamlined and focused.
FAQ
Can I use generated columns with existing tables?
Yes, you can add generated columns to existing tables using the ALTER TABLE statement. The syntax is ALTER TABLE table_name ADD COLUMN column_name ... GENERATED ALWAYS AS (expression).
Does system versioning have a big storage overhead?
It can, as it stores every historical version of a row. The impact depends entirely on how frequently your data changes. For audit-heavy applications, the trade-off for a complete history is usually worth it.
Is the new password validation plugin enabled by default?
No, it is not enabled by default. You must install and activate the simple_password_check plugin manually in your server configuration to start enforcing password policies.
What's the main benefit of the InnoDB optimizations?
The main benefit is better scalability under heavy write load. Applications that do a lot of concurrent inserts and updates will see reduced lock contention and improved overall throughput.
Should I be concerned about the deprecated InnoDB monitors?
If your monitoring scripts rely on the old INFORMATION_SCHEMA monitor tables, you should start migrating them to use the Performance Schema equivalents. The deprecated features will eventually be removed in a future release.