MariaDB + DuckDB: A New Playground for Analytics – A First Look at the New Storage Engine

MariaDB just announced it has learned to quack: the new DuckDB storage engine has joined the large family of storage engines in MariaDB Server.

The idea is very interesting: use MariaDB Server as usual, but create some tables using ENGINE=DuckDB and benefit from DuckDB’s columnar storage and vectorized execution for analytical queries.

In other words, we can keep our transactional workload in InnoDB, and use DuckDB tables for analytics… in the same MariaDB instance. Not a new concept, but a new and powerful implementation!

This is, of course, not something I would recommend for production today;

DuckDB Storage Engine for MariaDB. When the Sea Lion Learns to Quack.

An early look at the DuckDB storage engine for MariaDB — columnar, vectorized analytics that live right next to your transactional tables.

The problem

MariaDB’s InnoDB is excellent at what it was built for: transactions. Row-by-row inserts, updates, point lookups, strong consistency. But the moment you ask it to scan tens of millions of rows for a multi-way join with a few aggregations, a row store has to work hard.

The usual answer is to stand up a separate analytical system, then build ETL pipelines to copy data into it.

The Power Of The Community!

Inspired by some recent LinkedIn posts, I decided to take the AI in my own hands and do some stats on the MariaDB and MySQL repositories.

This graph is what I’ve got.

Not only have MariaDB Server distinct contributors surpassed the distinct MySQL Server contributors count! The External MariaDB contributors alone did! *

This is how the Power Of the Community looks like!

  • You get to use a more functional, performant and error free MariaDB Server
  • ⁠⁠You get a say in shaping the future of the MariaDB Server.

MariaDB Foundation: Bringing TPC-B Back To Life

When I joined Pervasive PSQL, one of the first performance test cases I was introduced to was TPC-B. It was already implemented inside Pervasive PSQL and it quickly became one of the most important tools in my daily work. A little later, another developer and I wrote the Pervasive PSQL’s TPC-C implementation in C++. Between those two workloads, and a few others, I spent nearly five years performing change testing. (https://en.wikipedia.org/wiki/Pervasive_Software)

During that time, about seventy percent of all regressions came from TPC-B, with the remaining issues coming from ATOMICs and TPC-C.

Virtuozzo Renews Sponsorship of MariaDB Foundation

We are delighted to announce that Virtuozzo has renewed its sponsorship of MariaDB Foundation.

Virtuozzo has been a long-standing supporter of open infrastructure, service providers, and cloud platforms, and we are very pleased to continue strengthening our collaboration.

At MariaDB Foundation, sponsorship is not only about financial support. It is also about building useful, practical ecosystem work around MariaDB Server together with organizations that care about open technology, reliable infrastructure, and long-term user choice.

With Virtuozzo, we see strong alignment around open cloud infrastructure, database performance, operational reliability, and practical deployment models for service providers, SaaS platforms, and enterprise environments. 

Vibe-coding an Audit Plugin in Under 3 Minutes

Who says developing MariaDB plugins is hard? I was able to produce one in under 3 minutes!

I of course did it by asking Grok nicely:

The produced result is actually very decent:

/*
errorwatch.c – MariaDB Audit API plugin

Records statement execution errors into a dedicated log file.

This plugin subscribes to the GENERAL audit class and logs
events of type MYSQL_AUDIT_GENERAL_ERROR (and STATUS events
that carry a non-zero error code). It writes structured
entries to /var/log/mariadb/errorwatch.log (or /tmp/ fallback).

To build (inside MariaDB source tree):
1. Copy this file and CMakeLists.txt to plugin/errorwatch/
2. …

Introducing Our First MariaDB Server Solution Stack: A Privacy-First Stack with Nextcloud, Passbolt, and MariaDB

MariaDB Foundation is pleased to announce the publication of our first MariaDB Server Solution Stack in the MariaDB Server Ecosystem Hub:

Privacy-First Stack: Nextcloud, Passbolt, and MariaDB Server

This stack brings together three open-source technologies with a shared purpose: helping organizations build collaboration infrastructure around privacy, control, and long-term digital sovereignty.

The stack combines:

  • Nextcloud for file sharing, synchronization, and collaboration
  • Passbolt for password, credential, and secrets management
  • MariaDB Server as the open-source relational database layer at the core

Together, they form a practical architecture for organizations that want to keep collaboration data, credentials, and structured data under their own control.

MariaDB Foundation releases the BETA of the Test Automation Framework (TAF) 2.5

The MariaDB Foundation is releasing the BETA version of the Test Automation Framework (TAF) 2.5. This release represents a significant architectural upgrade, strengthening the framework’s lifecycle model, profiling capabilities, extraction and install pipeline, and reporting consistency. The focus of the BETA is on determinism, clarity, and contributor‑proof behavior across the entire workflow.

TAF continues to serve as an open, reproducible framework for evaluating MariaDB builds, running performance workloads, collecting diagnostics, and validating behavior across versions. The 2.5 BETA builds on the earlier Alpha release by refining the internal architecture and expanding the framework’s ability to support community testing.