Latest in branch 10.7
10.7.8
Released 01 Feb 2023
(3 years ago)
SoftwareMariaDB
Version10.7
Status
End of life
Initial release10.7.1
05 Nov 2021
(4 years ago)
Latest release10.7.8
01 Feb 2023
(3 years ago)
Community EOL09 Feb 2023
(Ended 3 years, 3 months ago)
Enterprise EOLUnavailable
Extended EOLUnavailable
Release noteshttps://mariadb.com/docs/release-notes/community-server/old-releases/release-notes-mariadb-10-7-series/mariadb-10-7-8-release-notes
Source codehttps://github.com/mariadb/server/tree/mariadb-10.7.8
Documentationhttps://mariadb.com/kb/en/documentation/
MariaDB 10.7 ReleasesView full list

What Is New in MariaDB 10.7

MariaDB 10.7 is a short-term support release packed with incremental improvements and new features that refine the database engine. It focuses on enhancing existing functionality rather than introducing massive changes.

Category Key Changes
New Features System-versioned tables with BINLOG_COMMENT, FLUSH TABLES WITH READ LOCK timeout, New status variables
Improvements InnoDB performance and compression, Faster INFORMATION_SCHEMA queries, Optimizer enhancements
Security OpenSSL 3.0 support, mysql_native_password plugin deprecated
Deprecated & Removed Deprecated: InnoDB system tables, innodb_locks_unsafe_for_binlog. Removed: TokuDB storage engine

What are the key InnoDB enhancements?

InnoDB received several under-the-hood optimizations for better performance and efficiency. The improvements target compression, index building, and buffer pool management.

Compression for InnoDB tables is now more effective, reducing storage footprint. The process for adding indexes (online DDL) has been sped up significantly, which is a big win for large tables. These changes make InnoDB more robust for heavy workloads without altering application logic.

How is query performance improved?

Faster INFORMATION_SCHEMA queries and optimizer enhancements directly speed up database introspection and complex queries. Queries against metadata tables now return results much quicker.

The optimizer can now handle certain types of queries more efficiently, leading to better execution plans. This matters because it reduces latency for applications that rely on dynamic schema exploration or run complex reports.

What security updates were introduced?

Support for OpenSSL 3.0 is the headline security update, ensuring the database uses modern cryptographic libraries. This keeps connections secure and up-to-date with current standards.

The mysql_native_password plugin was officially deprecated in favor of the more secure ed25519 plugin. In practice, you should start migrating user accounts to the newer authentication method for better security.

What features were deprecated or removed?

TokuDB storage engine was completely removed from MariaDB packages. This was expected as its maintenance was discontinued. The InnoDB system tables and the innodb_locks_unsafe_for_binlog variable were deprecated.

If you were using TokuDB, you need to migrate your tables to another storage engine like InnoDB or MyRocks. The deprecation warnings for other features are a clear signal to update your scripts and configurations for future versions.

What new controls are available for system-versioned tables?

System-versioned tables now support the BINLOG_COMMENT option. This allows you to add a comment to the binary log when making changes to temporal tables.

This is useful for auditing purposes, as it lets you tag specific transactions in the binlog that relate to historical data changes. It provides more context for anyone parsing the binary logs later.

FAQ

Is TokuDB still available in MariaDB 10.7?
No, the TokuDB storage engine was completely removed from MariaDB 10.7 packages. You must migrate any existing TokuDB tables to an alternative engine like InnoDB before upgrading.

What should I use instead of mysql_native_password?
You should migrate to the ed25519 authentication plugin. It's more secure and is now the preferred method for password authentication in MariaDB.

How do the INFORMATION_SCHEMA improvements affect me?
Queries against metadata tables (e.g., SELECT * FROM INFORMATION_SCHEMA.TABLES) will execute significantly faster. This benefits monitoring tools and admin scripts that frequently access schema information.

What is the practical benefit of the FLUSH TABLES timeout?
The new WITH TIMEOUT option for FLUSH TABLES WITH READ LOCK prevents the command from hanging indefinitely if it can't acquire a lock. This makes backup scripts more robust and prevents them from stalling production systems.

Should I upgrade to MariaDB 10.7 for production use?
10.7 is a short-term support release. It's ideal for testing new features but for production, you might prefer a long-term support (LTS) version like 10.6 for greater stability and longer maintenance coverage.

Releases In Branch 10.7

VersionRelease date
10.7.801 Feb 2023
(3 years ago)
10.7.703 Nov 2022
(3 years ago)
10.7.613 Sep 2022
(3 years ago)
10.7.510 Aug 2022
(3 years ago)
10.7.418 May 2022
(4 years ago)
10.7.310 Feb 2022
(4 years ago)
10.7.206 Feb 2022
(4 years ago)
10.7.105 Nov 2021
(4 years ago)