Category Archives: Generic
Introduction
Over the past weeks, questions around Galera, high availability, and continuity have generated understandable concern within parts of the MariaDB community.
Clarity matters in moments like this.That is also why this response was unfortunately not immediate. It was important to understand the full picture and ensure that what we communicate reflects the actual state of responsibilities and decisions.
This post explains where things stand today, what has changed, and how the MariaDB Foundation views its role going forward. Directly. Transparently. With responsibility.
Galera and the community: acknowledging the reality
High availability has always mattered.
…
I wanted to share with you all some statistics on the incoming community contributions for the MariaDB server in the last year or so. And some of my thoughts looking at the data.
I’ve been quietly working on scripting some of my daily routines using the github CLI and the Jira REST API. Thanks to a question by Anna, the visionary MariaDB Foundation CEO, I’ve also created some scripts to fetch and summarize statistics on the incoming community contributions pull requests.
A picture’s worth a thousand words. So here we go:
This depicts the community pull requests opened or closed each month (the top graph).
…
Continue reading “The Rising Tide of Community Contributions to MariaDB Server”
The MariaDB Foundation is releasing the alpha version of the Test Automation Framework (TAF), an open-source benchmarking framework designed for clarity, repeatability, and vendor-neutral testing. TAF provides a structured way to run database benchmarks using consistent workloads, configuration, and reporting pipelines, making results easier to reproduce and discuss.
TAF has evolved into a modular system built around three plugin types: database maker plugins, test suite plugins, and report plugins. This architecture keeps the core stable while allowing contributors to extend the framework with new database engines, workloads, and reporting formats.
The alpha includes maker plugins for MariaDB and MySQL, test suites for Sysbench and HammerDB (TPROC-C and TPROC-H), and a set of report plugins for raw text, charts, and combined summaries.
…
Continue reading “MariaDB Foundation Releases Alpha of the Test Automation Framework (TAF)”
We are delighted to announce that Epsio (https://www.epsio.io/) has joined the MariaDB Foundation as an official silver sponsor.
Epsio’s commitment to innovation and open technology aligns closely with the mission of the MariaDB Foundation: to support and advance the MariaDB ecosystem and strengthen the long-term viability of MariaDB as a reliable, open source database platform. Their sponsorship will help fuel community initiatives, foster collaboration, and expand opportunities for developers and organizations around the world.
“We are excited to partner with Epsio,” said Anna, CEO at the MariaDB Foundation. “Their support is a meaningful contribution to our work and reflects shared values in open source, performance, and community empowerment.”
Epsio’s sponsorship will directly support the Foundation’s core activities, including community programs, developer engagement, and educational initiatives that drive the growth and sustainability of MariaDB globally.
…
Continue reading “MariaDB Foundation Welcomes Epsio as a Silver Sponsor”
The Debian project has today announced their 9th release, code named “Stretch”. This is a big milestone for MariaDB, because the release team decided to ship and support only one MySQL variant in this release, and MariaDB was chosen over MySQL.
This is prominently mentioned in the press release about Debian 9 and more information can be found in the Debian release notes. We have also written an article in the Knowledge Base about MySQL to MariaDB migration in Debian. Everything has been designed to work so that the upgrade from MySQL 5.5 in Debian 8 to MariaDB 10.1 in Debian 9 should be automatic and smooth. …
Continue reading “Debian 9 released with MariaDB as the only MySQL variant”
Usually when one says “SSL” or “TLS” it means not a specific protocol but a family of protocols. Wikipedia article has the details, but in short — SSL 2.0 and SSL 3.0 are deprecated and should not be used anymore (the well-known POODLE vulnerability exploits the flaw in SSL 3.0). TLS 1.0 is sixteen years old and while it’s still being used, new security standards (for example PCI DSS v3.1) require TLS 1.1 or, preferably, TLS 1.2.
MySQL used to support TLS 1.0 since 2001. Which means MariaDB supported it from the day one, and never supported weaker SSL 2.0 or SSL 3.0. …
InnoDB holepunch experiments
After excellent blogs by Mark Callaghan (see links below), I decided to use some of my time to experiment how different filesystems behave if the holepunch feature is used in MariaDB 10.1. First of all, MariaDB 10.1 does not use holepunch by default even if a table is page compressed (a term used in MariaDB). The holepunch feature in MariaDB is enabled with the innodb-use-trim=1 configuration variable and naturally requires support of the fallocate system call with the FALLOC_FL_PUNCH_HOLE and FALLOC_FL_KEEP_SIZE parameters. Support for these is checked during the cmake build phase.
I used CentOS Linux release 7.1.1503 (Core) using the 3.10.0-229.el7.x86_64 Linux kernel and few SSD drives in a RAID-0 setup (Intel X25-E Extreme SSDSA2SH032 G1GN 2.5-inch 32GB SATA II SLC Internal Solid State Drive (SSD)). …
Continue reading “InnoDB holepunch compression vs the filesystem in MariaDB 10.1”
Introduction
A foreign key is a field (or collection of fields) in one table that uniquely identifies a row of another table. The table containing the foreign key is called the child table, and the table containing the candidate key is called the referenced or parent table. The purpose of the foreign key is to identify a particular row of the referenced table. Therefore, it is required that the foreign key is equal to the candidate key in some row of the primary table, or else have no value (the NULL value). This is called a referential integrity constraint between the two tables. …
Continue reading “MariaDB: InnoDB foreign key constraint errors”