What Is New in MariaDB 11.7
MariaDB 11.7 is a feature-packed release focusing on performance enhancements, new SQL capabilities, and improved security. It builds upon the foundation of previous versions with significant optimizations for both developers and database administrators.
| Category | Key Changes |
|---|---|
| New Features | Generated Columns, System Versioning Improvements, New Functions |
| Performance | Optimizer Improvements, Faster Aggregation, InnoDB Enhancements |
| Security | Password Validation Plugin, Audit Plugin Updates |
| Deprecations & Removals | Old InnoDB System Variables, Obsolete Functions |
What new SQL features should I start using?
Generated columns are a major addition, allowing you to define columns whose values are computed from expressions involving other columns. This simplifies queries by pre-calculating values, reducing application logic. You can create them as VIRTUAL (computed on read) or PERSISTENT (stored on write).
System versioning sees improvements for temporal tables, making it easier to query historical data. New functions like BIN_TO_UUID() and UUID_TO_BIN() provide efficient handling of UUID values, which is crucial for distributed systems.
How is query performance improved?
The optimizer is smarter with derived tables and merges, often avoiding materialization for faster execution. Aggregation queries benefit from optimizations that reduce overhead during grouping operations.
InnoDB gets low-level enhancements for write efficiency and buffer pool management. In practice, this means better throughput for write-heavy workloads and more consistent performance under load.
What about security updates?
The simple_password_check plugin helps enforce basic password policies by validating password length and complexity. The audit plugin is updated for better compatibility and logging control.
These are incremental but important steps for hardening your database setup. They provide more tools to meet basic security requirements without heavy customization.
What has been deprecated or removed?
Several old InnoDB system variables like innodb_file_format are now deprecated and will be removed in a future release. Some obsolete SQL functions are also on the deprecation path.
This cleanup reduces code complexity and paves the way for future improvements. Check your configuration files and application code for references to these deprecated settings to avoid surprises later.
FAQ
Should I use generated columns for frequently accessed data?
For read-heavy workloads, PERSISTENT generated columns can improve performance by storing the computed value. For data that changes often but is read less, VIRTUAL columns save storage space at a minor CPU cost during reads.
Do the UUID functions work with standard UUID formats?
Yes, UUID_TO_BIN() and BIN_TO_UUID() handle standard UUID strings. They allow efficient storage as binary(16) which is much faster for indexing and comparisons than string-based UUIDs.
How do I enable the new password validation plugin?
Install the plugin and set the simple_password_check system variables to enforce policies like minimum length and required character types. It's a straightforward way to add basic password rules.
Will the optimizer changes break my existing queries?
No, the optimizer improvements are designed to be backward compatible. They provide better execution plans for many queries without changing the semantics of your existing SQL code.
What should I do about the deprecated InnoDB variables?
Review your my.cnf or my.ini configuration file and remove any references to deprecated variables like innodb_file_format. Their functionality is now handled automatically by MariaDB.