The latest from the MySQL community

1. Table(s) structure
2. The Tests
3. How to use it
4. How to modify it
   1. Method 1. 
   2. …

{index}

"What happens when you run a 10 TB MySQL database on Kubernetes?" 

That's the question many of our customers and users asked and honestly, we were extremely curious ourselves.

So, we ditched the weekend plans, rolled up our sleeves, and jumped down the rabbit hole. What we found was far more challenging (and perhaps a bit more "psychedelic") than expected. We spent days rigorously testing the Percona Operator for PXC at massive scale. 

This blog post distills all our findings into the most critical, actionable advice you need to ensure your high-scale environment not only survives but operates reliably.

If you are lazy and prefer to watch a video, here is the presentation I did at the MySQL Belgian days in January 2026. …

"What happens when you run a 10 TB MySQL database on Kubernetes?" 

That's the question many of our customers and users asked and honestly, we were extremely curious ourselves.

So, we ditched the weekend plans, rolled up our sleeves, and jumped down the rabbit hole. What we found was far more challenging (and perhaps a bit more "psychedelic") than expected. We spent days rigorously testing the Percona Operator for PXC at massive scale. 

This blog post distills all our findings into the most critical, actionable advice you need to ensure your high-scale environment not only survives but operates reliably.

If you are lazy and prefer to watch a video, here is the presentation I did at the MySQL Belgian days in January 2026.

First of …

ProxySQL 3.0.5: Security hardening, PostgreSQL protocol fixes, and smoother operations

We’re excited to announce ProxySQL 3.0.5, our first release of 2026.
As always, thank you to everyone who tested, reported issues, sent patches, and shared real-world feedback.
ProxySQL is shaped in production, and this release is a direct result of that collaboration.

ProxySQL 3.0.5 focuses on tightening security guarantees (especially for PostgreSQL TLS enforcement),
improving protocol correctness for PostgreSQL clients, and restoring compatibility knobs for MySQL
application stacks that are sensitive to version semantics.

Full release notes are available on GitHub:
https://github.com/sysown/proxysql/releases/tag/v3.0.5

What’s new in 3.0.5 (and why it matters) PostgreSQL …

In this guide, we explain 150+ SQL commands in simple words, covering everything from basic queries to advanced functions for 2026. We cover almost every SQL command that exists in one single place, so you never have to go search for anything anywhere else. If you master these 150 commands, you will become an SQL […]

Who has never encountered a customer who, for all sorts of reasons (valid or not), was unable to update an application and therefore could no longer connect to the latest versions of MySQL? Or worse still, data that is shared between two applications, one of which absolutely must use the latest version of MySQL and […]

Percona Toolkit 3.7.1 has been released on Dec 17, 2025. The most important updates in this version are:

• Finalized SSL/TLS support for MySQL
• Added support for Debian 13 and Amazon Linux 2023
• Fixed MariaDB support broken in version 3.7.0
• Added options to skip certain collections in pt-k8s-debug-collector and pt-stalk
• Documentation improvements
• Other performance improvements

In this blog, I will outline the most significant changes. A full list of improvements and bug fixes can be found in the release notes.

SSL/TLS support for MySQL

Percona Toolkit historically did not have consistent SSL support. This was reported at …

A lightweight, secure, and extensible MCP (Model Context Protocol) server for MySQL designed to bridge the gap between relational databases and large language models (LLMs).

I’m releasing a new open-source project: mysql-mcp-server, a lightweight server that connects MySQL to AI tools via the Model Context Protocol (MCP). It’s designed to make MySQL safely accessible to language models, structured, read-only, and fully auditable.

This project started out of a practical need: as LLMs become part of everyday development workflows, there’s growing interest in using them to explore database schemas, write queries, or inspect real data. But exposing production databases directly to AI tools is a risk, especially without guardrails.

…

MySQL replication has been around forever, and yet… people still manage to set it up in ways that break at the worst possible moment. Even in 2025, you can get burned by tiny schema differences, missing primary keys, or one forgotten config flag. I’ve seen replicas drift so far out of sync they might as well live in a different universe.

This guide covers the practical best practices—the stuff real DBAs use every day to keep replication stable, predictable, and boring. (Boring is a compliment in database land.)

Always Use GTIDs. Yes, Always.

GTID-based replication is one of those features that people resist turning on, and then once they do, they never want to go back.

Why GTIDs?

• Failover become sane
• Reparenting replicas stops being a headache
• Missing transactions are easy to detect

Your my.cnf should absolutely include:

Copy Copied!

In our earlier post, we unpacked the mechanics of MySQL HeatWave maintenance, the behind-the-scenes process that keeps your MySQL environments secure, stable, and optimized without changing your database version. We also touched on how Auto Minor Version Upgrades occur when a version reaches the end of its lifecycle. With this update, MySQL HeatWave introduces Configurable Maintenance Windows and Auto-Upgrade Controls, giving you […]