The latest from the MySQL community

TL;DR

Percona XtraBackup is a 100% open-source backup solution for Percona Server for MySQL and MySQL®. It is designed for high-availability environments, performing online, non-blocking, and highly secure backups of transactional systems without interrupting your production traffic.

While full backups work for small databases, large-scale systems rely on incremental backups to save space and time. However, the “prepare” stage, required to make the incremental backups consistent, was slow because XtraBackup processed the .delta files serially. The .delta files are generated per table and store only the modifications since the last backup.

Great news! In XtraBackup versions …

Last week, ProxySQL announced that they are taking over the maintenance and development of Orchestrator, the MySQL high-availability and topology management tool originally authored by Shlomi Noach. You can read their announcement here: Announcing the future of Orchestrator.

We want to briefly share Percona’s position on the news.

We welcome this

Orchestrator became the de facto standard for MySQL topology management and automated failover, and it has been a foundational tool in the ecosystem for over a decade. When the upstream project was archived, many operators were left running internal forks. A revived project under active development, with a stated roadmap and continued Apache 2.0 licensing, is good news for the MySQL community, and we’re glad to see ProxySQL step up to take it on. Thanks are due to Shlomi Noach …

In this ninth post of our series, we decode the XID_EVENT — the smallest event in the binary log, and the one that marks every transactional commit.

Introduction

Every DML transaction we've decoded so far ends the same way: with an XID_EVENT (event type 16, 0x10). At only 31 bytes on the wire, it carries a single piece of information — an 8-byte transaction identifier — but it does some of the heaviest lifting in MySQL replication. The XID_EVENT is what allows replication to be crash-safe with the default binlog_format = ROW and transaction-isolation = REPEATABLE-READ.

When the source commits a transaction that touches an XA-capable storage engine (in practice: InnoDB), it writes an XID_EVENT as the final event of the transaction in the binary log. The numeric XID …

Introduction Replication performance depends on every stage in the pipeline, from the source database to transport and ultimately to commit on the replica. On the replica side, much of that performance comes down to how efficiently changes are read, scheduled, and applied under real operational pressure. In practice, that directly affects steady-state lag, backlog recovery […]

Learn how to run MySQL on Kubernetes in regulated environments. This guide covers security controls, compliance requirements, auditability, encryption, access management, and operational best practices for production-grade deployments.

I have written a new post on the MySQL blog about the hypergraph optimizer, which is now available in MySQL 9.7 Community Edition.

The post gives a high-level technical overview of what is different from the classic join optimizer, why it can produce better plans for some multi-table queries, and where it is most useful to try. It also includes early benchmark results and some caveats, since the feature is still evolving and remains off by default.

On April 21, 2026, our third public discussion continued the conversation around transparency, participation, and the future of MySQL. Building on the momentum from earlier sessions, the discussion focused on progress and improvements to increase community transparency and practical ways for community members to get involved. At the center of the discussion was the MySQL […]

MySQL 9.7 Community Edition now includes the hypergraph optimizer as an alternative to the classic join optimizer, making this capability available across all MySQL editions. This is not a cosmetic change. The hypergraph optimizer uses a new join-planning framework aimed at queries where plan shape can make a real difference, particularly for multi-table joins, workloads […]

When vertical scaling, read replicas, and MEMORY tables weren't enough, Readyset's SQL-level caching broke through the ceiling, delivering over 109,000 queries per second on MySQL.

Key Results

109K

Queries Per Second

0

Lines of Code Changed

<1ms

Cached Query Latency

8x

Read Throughput Increase

About Lemit

Lemit (Lemit Tecnologia da Informacao) is a Brazilian data enrichment and credit intelligence company based in Sao Paulo. Their platform enables businesses to make faster, more accurate credit decisions by enriching, qualifying, and cleansing customer data at scale, powering individual lookups, batch integrations, and real-time API queries across millions of records with 100% all-flash storage.

"Using Readyset with our existing …

When people ask me how to tune MySQL, they usually mean, “Which variables should I change in my.cnf?” (the MySQL configuration file) That certainly is a reasonable place to start, because most day-to-day performance tuning really is driven by MySQL itself: memory allocation, redo flushing, connection handling, temporary tables, and InnoDB I/O behavior. But the […]