MariaDB 13.0 Is Now Stable

MariaDB Server 13.0 is now Stable!

The 13.0 series started its journey in March 2026 with the Preview. It then progressed through the Release Candidate phase and is now ready for general use as MariaDB’s latest Stable rolling release.

This is not a long-term support release, which means that an upgrade is relevant for you in the specific scenario that you want to try one of the new features described below. In a test or production environment. But this is not an LTS.

13.0.2, Stable, is an important milestone.

From a Chocolate Wrapper to Concurrent InnoDB Page Splits

This work started from a conversation with Monty Widenius at Meet Magento Czech in August. We discussed possible ways to improve the scalability of the InnoDB B+Tree, especially its insert path and page splits.

Monty explained several ideas about reducing synchronization during structural changes and allowing independent parts of the tree to make progress concurrently. We did not have a whiteboard, so we made the first design sketch on the back of a dark chocolate wrapper.

The sketch contained a small B+Tree, several page links, and the basic idea of moving structural work outside the globally serialized path.

Extending MariaDB with Native Aggregate Plugins: Laying the Groundwork for HyperLogLog

MariaDB already allows developers to add new Pluggable Data Types and scalar Plugin Functions. One missing piece has been Pluggable Aggregate Functions operating on PDTs. That matters for functionality such as HyperLogLog, where an extension needs to aggregate values into a custom statistical sketch while preserving its native SQL type.

MDEV-40672 closes that architectural gap. Aggregate functions can now participate in MariaDB’s native aggregation infrastructure, including DISTINCT, window execution, prepared statements and Pluggable Data Types.

MariaDB already supports MariaDB_FUNCTION_PLUGIN, a mechanism for registering SQL functions that create regular server Item objects and can behave almost like built-in functions.

MariaDB Foundation Advances TAF with HammerDB 6.0 and xt_reservoir Integration

Overview

While validating MariaDB RSS stability under stored procedure workloads, I ran into unexpected memory growth. The goal was straightforward: confirm that MariaDB was not leaking memory when running TPROC-C stored procedure workloads. To do this, I used HammerDB TPROC-C SP and added improved RSS monitoring so I could watch memory usage over long-duration runs.

The results were clear. MariaDB RSS stayed stable. HammerDB 5.0 kept growing, and growing.

This led to a deeper investigation into HammerDB itself, and ultimately to an update in TAF to support HammerDB 6.0 and a new RSS logging script.

Hear Ye, Hear Ye: A Guide to MariaDB’s Governance Model

Be it known: MariaDB Server now has a clearer, publicly documented governance framework covering technical roles, subsystem ownership, decision-making, response expectations and continuity.

Open source begins with access to the code. Yet for infrastructure expected to remain dependable for many years, openness must also extend to how responsibility is assigned, how decisions are made, and what happens when people disagree or move on.

The framework formalises much of how the project has long worked, while making its responsibilities, decision paths and commitments clearer and easier to inspect.

The central principle is simple: authority should be visible, earned and connected to responsibility.

Say the Name: MariaDB, MySQL, and the Ecosystem We Share

Names are important.

They help us identify people, projects, products, pets, database servers, and occasionally the correct bug tracker.

This may sound obvious, but the database world has spent more than fifteen years proving that it is not.

MySQL and MariaDB share a substantial amount of history, syntax, tooling, knowledge, applications, and community. They also have similar command names, compatible protocols, familiar configuration variables, and many users who simply say “MySQL” when they actually mean:

Some database server that speaks the MySQL protocol and probably has an executable named mysqld.

And most of the time, everybody understands.

Continuent joins MariaDB Foundation as a Silver Sponsor

MariaDB Foundation is pleased to welcome Continuent as a new Silver Sponsor.

Continuent develops solutions for organizations running business-critical applications on MariaDB and other MySQL-compatible databases. Its flagship product, Tungsten Cluster, helps organizations manage database availability, disaster recovery and distributed deployments across on-premises, cloud and hybrid environments.

The company has worked with open-source database technologies for more than two decades and brings extensive experience from demanding production environments across SaaS, financial services, telecommunications, e-commerce and other industries.

“Continuent has a long history in the MariaDB and wider open-source database ecosystem.

Nextcloud renews its Silver sponsorship of MariaDB Foundation

MariaDB Foundation is pleased to announce that Nextcloud has renewed its Silver sponsorship for another year.

Nextcloud and MariaDB are widely used together by organisations that want greater control over their data and infrastructure. Both projects form part of a broader open-source ecosystem that enables businesses, public-sector organisations and individuals to build digital services without unnecessary dependence on proprietary platforms.

Over the past year, our collaboration has also developed through the Privacy-First Solution Stack, which brings together Nextcloud, Passbolt and MariaDB Server in a practical open-source architecture for secure collaboration, password management and data storage.