MariaDB 12.3.2

Remember when MariaDB was just "MySQL without the Oracle baggage"? That was 2009. Sixteen years later, MariaDB 12.3.2 ships as a Long Term Support release — maintained until June 2029 — and it barely resembles the fork that started it all.

The Binary Log: Rewritten from the Ground Up

The single biggest change in MariaDB 12.3 is the new binary log implementation. What began as a simple replication log in MySQL 3.23 has been completely rearchitected: binary log events can now be stored in InnoDB-managed storage instead of relying solely on traditional separate files. The result? Up to 4x better write performance in replication-heavy workloads, according to MariaDB's benchmarks. For high-throughput environments, this changes the replication story entirely.

Vector Search Comes of Age

MariaDB's VECTOR data type, introduced in the 11.x series, gets significant performance optimizations in 12.3.2. Vector search queries — increasingly critical for AI workloads, semantic search, and embedding storage — now run dramatically faster. MariaDB isn't trying to be a dedicated vector database, but for applications that need basic vector capabilities alongside relational data, this release closes the gap considerably.

Oracle Compatibility Deepens

12.3.2 continues MariaDB's long march toward Oracle compatibility. New functions like TO_DATE and TO_NUMBER have been added, making migrations from Oracle less painful. The XML data type, which debuted in 12.3.1, is now stable. For teams migrating legacy Oracle workloads, each release removes another barrier.

The Long View

MariaDB 12.3.2 is a landmark release not because of any single feature, but because of what it represents. The project that started as a drop-in MySQL replacement has evolved into a database with its own identity — vector search, a custom binary log, deep Oracle compatibility, and a six-year LTS commitment. What began in 2009 as insurance against Oracle's acquisition of MySQL has become, sixteen years on, a serious independent platform.