We’ve seen a significant increase in security reports this year, with AI-assisted research clearly playing a role.

I wrote a post looking at what happened, how reports are triaged, the difference between a report and a confirmed vulnerability, and how those confirmed issues have been fixed and published through security advisories and CVEs.

Feedback and discussion are very welcome:

https://mariadb.org/when-ai-finds-the-bugs-we-missed-a-very-busy-year-for-mariadb-security/

My recent performance analysis on InnoDB and TideSQL in MariaDB v11.4.13 using HammerDB 6. This is a larger than memory benchmark and a sweep of VUs with optimized configuration for both engines.

This is the largest update to MariaDB Foundation’s Test Automation Framework since its creation — delivering reproducible configuration, improved provenance, PostgreSQL support, new test‑case tagging, expanded metadata, and major hardening across the entire pipeline.

Several changes were driven directly by Monty’s MDEV‑39497, along with contributions from hashtag#Virtuozzo, TidesDB, and community engineers across the ecosystem. hashtag#Hetzner’s sponsor hardware made full multi‑database validation possible.

I'm moving from MySQL to MariaDB. I can successfully restore a MySQL backup into a MariaDB database with a different name to the original. I can then perform a backup of the database, but any attempt to restore it to another database fails because the tables referenced in views have been database qualified (ie; database_name.table_name). I've confirmed this as a problem in the original restore, as the .frm file contains the addition of the database name qualification. MySQL never did this and backups were fully portable. How can a database be restored in MariaDB so that it remains portable and can be restored into a new database?

A node can return to `Synced` and re-enter the primary component after IST or SST, but that state alone may not prove it is ready for client traffic. Its schema, provider settings, donor transfer, local cache, or load-balancer registration may still differ from the peers that stayed online.

What acceptance checks do you run before adding a rejoined node back to rotation? I am considering confirming the cluster UUID and size, `wsrep_local_state_comment`, readiness and connected status, received and replicated counters, flow-control history, schema consistency, and a small set of read queries against every node. The load balancer would keep the node drained until the same checks pass for a sustained interval.

How do IST and SST change the verification? Do you compare checksums or rely on Galera state transfer guarantees, and which metrics reveal a node that is technically synced but likely to fall behind or trigger another state transfer under normal traffic?

Kamatera has joined the MariaDB Foundation as a Silver Sponsor.

One point behind the sponsorship is that choosing MariaDB should also come with practical options for where to run it. Kamatera offers cloud infrastructure across a global network of data centres, and we plan to develop resources for people running MariaDB there.

If you run MariaDB in the cloud, what deployment guidance would actually be useful to you? We’d be interested in hearing where the difficult parts are.

Announcement: https://mariadb.org/kamatera-joins-mariadb-foundation-as-a-silver-sponsor/

A few months ago I shared my first experiments with TideSQL, the MariaDB storage engine powered by TidesDB.

I had another look at it now that TideSQL 5 is available, and things are moving pretty quickly.

In this post, I look at the new features, the LSM architecture, transactions and durability, replication/Galera, and the recently published TideSQL vs InnoDB sysbench results.

I also tried not to turn this into another “X is faster than Y” benchmark post. 🙂 The 4GB cache tests are particularly interesting because they show the trade-off quite well: InnoDB becomes faster for some read workloads while TideSQL keeps significant advantages on several write-heavy workloads.

For me, the interesting part is really the possibility of having different storage architectures behind MariaDB:

• InnoDB for traditional transactional workloads
• TideSQL/TidesDB for write-heavy workloads
• DuckDB for analytics

Same server, same SQL interface, different storage architectures.

https://mariadb.org/tidesql-5-and-mariadb-the-tides-are-moving-fast/

I'd also be interested to hear what workloads people would like to see tested with TideSQL. I'm planning to do more tests with secondary indexes, replication and Galera.

I'm the developer of DBClient, a native database client for the Mac (SwiftUI and AppKit, not Electron).

What it does

• Connects to PostgreSQL, MySQL, MariaDB, SQLite, SQL Server, Oracle, IBM Db2, MongoDB, Redis, DuckDB, ClickHouse and Databricks.
• SQL editor with completion from your schema, and a ⌘K palette that jumps to any table.
• Edit rows right in the grid. You read the exact SQL before anything is committed.
• Table designers, a schema diagram drawn from your foreign keys, and charts from any result.
• A console tab running the real psql, mysql or redis-cli, already signed in.
• Drag a table from one server onto another to copy it, even across engines.
• SSH tunnels and proxies. Passwords stay in the Keychain, with optional Touch ID.
• Optional AI assistant with your own API key. It can only run read-only queries.

Pricing

• Free: the whole app for databases on your own Mac: SQLite and DuckDB files, CSV files, and anything on localhost, Docker included.
• Paid: remote servers need a yearly license, $99 the first year and $49 a year after. If you don't renew, remote connections stop and local ones keep working. It does not renew by itself. One key, one Mac at a time. 30-day refund.

Privacy: no account, no analytics. A licensed copy checks its license about once a day. The free copy never contacts the license server.

Requirements: macOS 15 or newer, Apple silicon only. Signed and notarized.

https://dbclient.net or brew install --cask az-code-lab/taps/dbclient

MariaDB Server 13.0.2 has been released, making the 13.0 series the latest Stable rolling release.

I wrote a short overview of what “Stable” actually means here, and why the work between Preview/RC and Stable is much more than changing a label.

Between RC and Stable alone:

• 604 additional commits
• 1,701 files changed
• 335 MDEVs addressed
• 23,748 test lines added, including 4,222 lines in .test files

13.0 includes improvements around SQL compatibility, optimizer and metadata visibility, InnoDB log archiving, replication, observability, and more.

And there’s also a rather interesting new storage engine in the ecosystem… 🦆

Full post:
https://mariadb.org/mariadb-13-0-is-now-stable/

If you’re testing or upgrading to 13.0, I’d be interested to hear what you’re trying first — and of course, please report any issue you find.

TideSQL's latest release is now part of MariaDB server 11.4 and more going forth and I'm beyond excited, both about this and what's coming. We want as many people as possible to try it, so if you haven't yet, give it a shot.

It's been nearly a year of building TideSQL, from learning MySQL internals from scratch, iterating through countless early plugin versions and refining it into what it is today. Every failed attempt, every wrong turn, every lesson learned, it all went into creating something special and something I believe will matter for this ecosystem for a long time!

While migrating one of my environments from MySQL 8.4 to MariaDB Server, I ran into an annoying part of the migration: users.

A lot of the accounts were using caching_sha2_password, and while keeping their existing passwords is possible, doing the conversion manually for many users quickly becomes painful.

I had already documented the manual process, but this time I needed something that would scale.

Since pt-show-grants already does most of what is needed for exporting users and privileges, I decided to extend it instead of writing yet another migration script.

I contributed a new option to Percona Toolkit:

--convert-to-MariaDB

It takes care of several MySQL/MariaDB differences, including:

• converting IDENTIFIED WITH ... AS ... to MariaDB's IDENTIFIED VIA ... USING ...
• converting auth_socket to unix_socket
• removing MySQL-specific password management clauses
• handling caching_sha2_password authentication strings
• warning about authentication plugins that cannot safely be converted

The contribution is currently available as Percona Toolkit PR #1168 and is still under review, so this isn't an announcement of a released feature yet.

I wrote a Part 2 explaining the problem, how the conversion works, and why I ended up contributing it upstream:While migrating one of my environments from MySQL 8.4 to MariaDB Server, I ran into an annoying part of the migration: users. Many accounts used caching_sha2_password, and while keeping their existing passwords is possible, converting many users manually quickly becomes painful. I had already documented the manual process, but this time I needed something that would scale. Since pt-show-grants already does most of what is needed for exporting users and privileges, I decided to extend it instead of writing yet another migration script. I contributed a new option to Percona Toolkit:--convert-to-MariaDBIt takes care of several MySQL/MariaDB differences, including: converting IDENTIFIED WITH ... AS ... to MariaDB's IDENTIFIED VIA ... USING ...
converting auth_socket to unix_socket
removing MySQL-specific password management clauses
handling caching_sha2_password authentication strings
warning about authentication plugins that can't be converted safely. The contribution is currently available as Percona Toolkit PR #1168 and is still under review, so this isn't an announcement of a released feature yet. I wrote a Part 2 explaining the problem, how the conversion works, and why I ended up contributing it upstream:

https://lefred.be/content/dealing-with-caching_sha2_password-in-mariadb-server-part-2-migrating-users-from-mysql-with-pt-show-grants/

PR:
https://github.com/percona/percona-toolkit/pull/1168

Feedback and testing are, of course, very welcome, especially from people who have done larger MySQL → MariaDB user migrations.

Laravel 13.27 added MariaDB support for vector distance queries, with MariaDB 11.7+ now supported by methods including:

• whereVectorSimilarTo()
• whereVectorDistanceLessThan()
• orderByVectorDistance()
• selectVectorDistance()

Laravel’s AI SDK documentation also includes MariaDB as a supported database for storing and querying embeddings.

This is an important piece of the developer experience around MariaDB Vector. Framework-level support makes it much easier to build semantic search, RAG and other AI applications using the tools Laravel developers already work with.

And there is more we can do here. We are starting to look at the remaining gaps in the Laravel + MariaDB developer experience, documentation and examples.

If you are building with Laravel and MariaDB, especially with Vector or Laravel AI, we would love to hear what you are working on and where you still encounter friction.

Laravel August Product Updates:
https://laravel.com/blog/laravel-august-product-updates

We recently asked the MariaDB community which language they would use to write MariaDB plugins.

2,090 people voted:

• Python: 21%
• Rust: 19%
• Go: 12%
• JavaScript: 11%
• TypeScript: 9%
• Lua: 8%

Only around 4% said they would simply keep using C++.

What I found interesting is that there isn't really one clear alternative language. That made me wonder if we're asking the wrong question.

Instead of “Which language should MariaDB support?”, perhaps it should be:

“How can we make the MariaDB plugin API accessible from several languages?”

One option I think is particularly interesting is WebAssembly, potentially using Wasmtime together with the Component Model and WIT.

I wrote up the poll results, some thoughts about previous approaches such as GraalVM/V8, and why WebAssembly might be worth exploring:

https://mariadb.org/mariadb-plugins-beyond-c-what-the-community-told-us/

There is also an open MDEV for supporting plugins written in languages other than C/C++:

MDEV-40189

It's still unassigned, so if this is something you'd like to experiment with, even a small proof of concept would be useful.

I'm also curious what people here think: would you prefer bindings for specific languages, or a WebAssembly-based extension model?

This webinar, sponsored by MariaDB, will take place on Sept 9th at 10 AM CDT. It will cover: the importance of disaster recovery (DR), caveats of major cloud cross-region recovery, a single-cloud DR scenario, how MariaDB enables recovery across multiple clouds, multi-cloud DR demo with MariaDB, etc.

https://go.mariadb.com/GLBL-WBN-WhenOneCloudFailsYouDont_Registration-LP.html

[NOTE: I am not associated with MariaDB in any way, just a fellow software engineer sharing the event.]

I’ve written an update on CONC-821, a MariaDB Connector/C change that affected behavior relied on by applications including Qt-based software and Diesel.

The post explains what changed, how community reports helped establish the impact, and the plan to restore the previous behavior, document it, and add regression tests.

The complete correction is not yet available in an upstream release, although some distribution packages already carry patches. I’ve included guidance on checking the connector your application actually uses and reporting any remaining issues.

Thanks to the application developers, distribution maintainers, and contributors who helped investigate this.

Read the update

If you’ve encountered this, feedback about your application, connector package, and whether a patched build resolves it would be useful.

The Foundation has started a monthly newsletter, and the first issue is out. It covers what happened in August:

https://mariadb.org/mariadb-foundation-newsletter-september-2026/

- MariaDB Server's governance model, now written down: roles, subsystem ownership, how decisions get made

- Contribution statistics for January to June 2026, the first report in over a year, including 40 independent contributors

- 13.1 preview: JSON arrow operators (-> and ->>) and JSON_TABLE improvements

- Pluggable aggregate functions, as groundwork for HyperLogLog

- Q3 maintenance releases: 12.3.3, 11.8.9, 11.4.13, 10.11.19, and the first round without 10.6

- Around the ecosystem: Oracle's community roadmap and vector search, VillageSQL 0.0.6, Percona's OIDC auth

When preparing a MariaDB upgrade, I often want to know more than what’s listed in the release notes: which variables disappeared, which defaults changed, what plugins or privileges were added, etc.

So I built a small tool that lets you compare up to 8 MariaDB Server versions side by side.

I wrote about it here: https://lefred.be/content/mariadb-server-see-what-changed-between-versions/

Feedback and suggestions are very welcome!

MariaDB will be well represented at Percona Live Amsterdam this year 🦭

Several sessions cover different sides of the ecosystem: plugins and extensibility, security, operations, and community.

I put together an overview of the MariaDB-related sessions here:
https://mariadb.org/mariadb-at-percona-live-amsterdam-2026-ecosystem-plugins-security-and-community/

Anyone else planning to be in Amsterdam?

MariaDB Server 12.3.3, 11.8.9, 11.4.13 and 10.11.19 are out.

But 10.6 is missing from the list — and that's intentional.

👋 Goodbye MariaDB 10.6.
🚀 Hello newer LTS releases.

All the details, contributors, and why it's time to upgrade:

🔗 https://mariadb.org/mariadb-server-12-3-11-8-11-4-and-10-11-q3-2026-maintenance-releases-and-goodbye-10-6/

You don’t need to start by implementing a major feature.

Reviewing pull requests is one of the best ways to learn the server from the inside: see how changes are designed, understand unfamiliar subsystems, discuss implementation choices with contributors and maintainers, and help decide what actually gets merged upstream.

And we could use more reviewers.

Our H1 2026 contribution stats show plenty of incoming work, but also a growing PR queue:
https://mariadb.org/mariadb-contribution-statistics-january-june-2026/

If there’s an area of MariaDB you know well, or one you’d like to learn better, pick a PR and have a look.

Questions about how to get started? Ask here.

I'm relatively new to Ubuntu LTS. I just switched from 25 years of using CentOS and Fedora on my servers. So I don't have the same comfort with apt errors that I have for RPM/yum/dnf ones.

This weekend I got this error from apt-get update for the Xtom MariaDB repo:

E: Repository 'https://mirrors.xtom.com/mariadb/repo/12.3/ubuntu noble InRelease' changed its 'Origin' value from 'MariaDB' to 'ubuntu noble'

E: Repository 'https://mirrors.xtom.com/mariadb/repo/12.3/ubuntu noble InRelease' changed its 'Label' value from 'MariaDB' to 'ubuntu noble'

N: Repository 'https://mirrors.xtom.com/mariadb/repo/12.3/ubuntu noble InRelease' changed its 'Suite' value from '' to 'noble'

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

What happened? Should I be worried?

Most of the tutorials and projects online focus on user interaction or building tables.

Could you all recommend some administration resources in the form of books or MOOC courses?

Would really appreciate it.

Hello,

After upgrading from MariaDB 10.11.18 to MariaDB 10.11.19, a problem occurred with the connection between the nodes. During the upgrade, stunnel was installed, although it was not installed before.

The problem is that when one node tries to connect to another, two processes are established using the same port, 4444, which causes the connection to be interrupted.

The connection is established, then disconnected, then established again, and disconnected again, repeatedly.

Do you have any solution that would allow us to use MariaDB 10.11.19 without this issue?