Latest in branch 12.1
12.1.2
Released 13 Nov 2025
(6 months ago)
SoftwareMariaDB
Version12.1
Status
End of life
Initial release12.1.1
04 Aug 2025
(10 months ago)
Latest release12.1.2
13 Nov 2025
(6 months ago)
Community EOL13 Feb 2026
(Ended 3 months ago)
Enterprise EOLUnavailable
Extended EOLUnavailable
Release noteshttps://mariadb.com/kb/en/release-notes-mariadb-12-1-series/
Source codehttps://github.com/mariadb/server/tree/mariadb-12.1.2
Documentationhttps://mariadb.com/kb/en/documentation/
MariaDB 12.1 ReleasesView full list

What Is New in MariaDB 12.1

MariaDB 12.1 is a community release introducing several key enhancements focused on performance, security, and compatibility. The update includes new features, significant improvements to existing functionality, and a host of bug fixes.

Category Key Changes
New Features New PERFORMANCE_SCHEMA instrumentation, ALTER TABLE ... RENAME COLUMN statement.
Improvements Faster CHECK TABLE operations, enhanced optimizer statistics, better parallel replication.
Security OpenSSL 3.2 support, new caching_sha2_password authentication plugin.
Bug Fixes Resolved issues in replication, InnoDB, and the query optimizer.

What performance enhancements were made?

The performance of CHECK TABLE operations for InnoDB tables received a major boost. This is a big deal for DBAs who need to verify table integrity on large datasets, as it significantly reduces the time required.

Optimizer statistics handling was also improved, leading to more efficient query execution plans. This means your complex joins and subqueries should run faster and more predictably out of the box.

What new SQL syntax is available?

You can now use the standard SQL syntax ALTER TABLE ... RENAME COLUMN. This is a welcome addition for developers who prefer standard compliance over the older MariaDB/MySQL-specific CHANGE COLUMN syntax.

ALTER TABLE my_table RENAME COLUMN old_name TO new_name;

In practice, this makes schema migrations and refactoring scripts cleaner and more portable across different database systems.

How was monitoring improved?

New instrumentation was added to the PERFORMANCE_SCHEMA, providing deeper visibility into the server's internal operations. This allows for more granular performance troubleshooting.

You can now get better metrics on areas like prepared statement handling and metadata locking, which are often sources of contention in highly concurrent applications.

What security updates are included?

Support for OpenSSL 3.2 was added, ensuring the database can leverage the latest cryptographic libraries and security fixes provided by the OpenSSL project.

A new authentication plugin, caching_sha2_password, was introduced. This improves upon the existing sha256_password plugin by caching credentials in memory, which can help reduce authentication overhead for frequent connections.

Were there any replication fixes?

Yes, several issues related to parallel replication were resolved. These fixes improve the reliability and consistency of replication in scenarios with high write loads.

This matters because it reduces the chance of replicas falling behind or encountering errors, which is critical for maintaining healthy high-availability setups.

FAQ

Is the new ALTER TABLE ... RENAME COLUMN syntax backwards compatible?
Yes, it is fully backwards compatible. The old CHANGE COLUMN syntax remains available and unchanged. The new syntax is simply an additional, more standard way to achieve the same result.

Does the faster CHECK TABLE require any configuration?
No, the performance improvement for CHECK TABLE on InnoDB tables is enabled by default. You get the speed boost immediately without any need to adjust your server configuration.

What is the benefit of the caching_sha2_password plugin?
The main benefit is performance during authentication. By caching the hashed password in memory after the first successful connection, it eliminates the need for a full password exchange on subsequent connections from the same user, reducing latency.

Were there any specific InnoDB bug fixes?
Yes, the release notes mention fixes for specific issues within the InnoDB storage engine. These fixes address problems that could lead to crashes or incorrect behavior, enhancing overall stability.

Should I expect any changes to query plans due to optimizer improvements?
It's possible. The improvements to optimizer statistics mean the query planner may choose different, more efficient execution plans for your queries. It's always a good idea to monitor performance after an upgrade, though the changes are generally for the better.

Releases In Branch 12.1

VersionRelease date
12.1.213 Nov 2025
(6 months ago)
12.1.104 Aug 2025
(10 months ago)