The latest from the MySQL community

As organizations modernize their data platforms, MySQL HeatWave has emerged as a powerful solution for running online transactional processing (OLTP) and real-time online analytics processing (OLAP) together without ETL complexity. However, achieving optimal performance and cost efficiency requires thoughtful capacity planning. This blog explains how to monitor and estimate MySQL HeatWave capacity using SQL queries, […]

Modern cloud applications are expected to remain available even during infrastructure interruptions, replication failovers, maintenance events, and transient network failures. In distributed database environments, it requires applications to treat transient failures as a normal part of production operations. This blog discusses practical API reliability designs for applications using MySQL HeatWave High Availability and Read Replicas, […]

ProxySQL 3.0.8 extends session-variable tracking beyond parsed SET statements by consuming MySQL session-state notifications from backend OK packets.

Modern AI systems increasingly rely on multimodal data: text, images, documents, audio, and video. Among these modalities, image understanding has become one of the most important capabilities for AI-powered applications.
Traditionally, implementing these capabilities required specialized computer vision infrastructure, external vector databases, custom ML pipelines, and multiple frameworks.
With MySQL HeatWave GenAI, many of these capabilities can now be implemented directly inside SQL workflows using built-in AI routines.
In this article, we will build the foundations of a Vision Model Evaluation Assistant using MySQL HeatWave GenAI. The objective is not to create another image classifier, but rather a semantic image understanding platform.

The post Building an AI Vision Search Engine with MySQL …

In this eleventh and final post of our series, we decode the GTID_TAGGED_LOG_EVENT — the event MySQL 8.4 introduced to carry user-defined tags alongside the classic UUID and GNO, and along the way meet the new mysql::serialization framework that encodes it.

Introduction

Back in Part 5 we deferred one event: the GTID_TAGGED_LOG_EVENT (event type 42, 0x2a). It was introduced in MySQL 8.4 to support tagged GTIDs, which extend the classic UUID:GNO form with an optional user-defined label:

55778904-0299-11f1-b1b8-4ef0c4956feb:mytag:3
└────────── SID (UUID) ───────────┘ └tag┘ └GNO

A tag …

Following the strong engagement across the first three editions of our Public MySQL Community Discussion series, we’re pleased to invite you to Edition #4. We will focus on the upcoming contribution process changes and our Contributor Summit later in May. This ongoing series is part of our commitment to increase transparency, strengthen collaboration, and provide […]

MySQL 9.7 LTS Support Lands Released May 8, 2026 · GitHub Release

v1.26.5 introduces a MySQL Component build for MySQL 8.4 LTS and 9.7 LTS, a unified logging abstraction, and a set of plugin stability fixes. The plugin path for MySQL 8.0, 8.4, and 9.0 is unchanged.

Why the Component architecture matters

MySQL has been deprecating the legacy plugin API in favor of the Component architecture since 8.0. Components install via INSTALL COMPONENT, integrate through typed service interfaces, and are better isolated from server internals — meaning fewer breakages across MySQL minor versions and a supported path forward as the plugin API winds down. For MyVector, this move isn’t optional in the long run: the component model is where MySQL’s extension ecosystem is heading, and building on it now means users on …

In modern application development, observability is no longer optional. It is a core requirement for stable operations, faster troubleshooting, and better understanding of system behavior. Databases are especially important because they often sit at the center of application performance. When a database becomes slow, overloaded, or unavailable, the impact is usually felt across the entire […]

In this tenth post of our series, we decode the ROTATE_EVENT — the event that closes a binary log file and tells every reader, replica or local, where to look next.

Introduction

The ROTATE_EVENT (event type 4, 0x04) is the bookmark MySQL leaves at the end of a binary log file. It carries two pieces of information:

• The name of the binary log file to read next.
• The starting position within that next file (always 4, the byte right after the 4-byte magic number from Part 2).

Together those two fields are enough for any reader — a replica's I/O thread, a mysqlbinlog invocation, a CDC tool — to seamlessly continue from one file into the next. …

May 2026 · 5 min read. Alkin Tezuysal

Cross blog from Oracle https://blogs.oracle.com/mysql/mysql-9-7-is-out-and-the-community-wins

MySQL 9.7 came out on April 21 and I’ve been going through the release notes so you don’t have to. The short version: Oracle has made several previously Enterprise-only features available in the Community Edition; the Hypergraph Optimizer is now free for everyone; and if you’re still on MySQL 8.0, it has reached End-of-Life. Like right now. We’ll get to that.

Let’s go through what matters most.

First: MySQL 8.0 has reached End-of-Life

MySQL 8.0.46 shipped alongside 9.7, and it is the last 8.0 release. As of April 2026, 8.0 is officially End-of-Life. No more security patches. No …