Planet MySQL HA Blog
The Planet MySQL HA Blog aggregates content from sources that cover topics related to high availability (HA) for MySQL databases.
Mapping your data to file(s) in your Lakehouse table
MySQL HeatWave is a fully-managed MySQL database service that combines transactions, analytics, machine learning, and GenAI services, without ETL duplication. Also included is HeatWave Lakehouse, allowing users to query data stored in object storage, MySQL databases, or a combination of both. Introduction In the 9.6.1 release of MySQL HeatWave, Lakehouse now supports the _metadata_filename column […]
MySQL Community Early Access Builds
MySQL benefits from a large and technically rigorous community—people who run MySQL at scale, test it in diverse environments, and surface issues (and ideas) that make the product better. Over the last year, we’ve been listening to community feedback and, since January 2026, sharing our updated community engagement approach (see: A New Era of MySQL Community […]
Join the Public MySQL Community Roadmap Discussion Webinar (Edition #2)
Following the strong participation in our first Public MySQL Community Roadmap Discussion (with attendees joining from around the world), we are excited to invite you to the second edition of this public community webinar series. In our latest blog post, we have published a brief recap of the first webinar—highlighting the key roadmap themes, how […]
Building a MySQL Shell Plugin to Scan for Sensitive Data (Vibe Coding AI-assisted, ~30 minutes)
Sensitive data has a way of showing up in unexpected places: an “email” column in a demo app, a forgotten “token” field in a logging table, or free-text notes that quietly become regulated data. I wanted a lightweight, repeatable way to answer a simple question on any MySQL instance: Where is sensitive data likely to […]
Active-Active MySQL Group Replication Best Practices
In MySQL Group Replication (MGR) or Group Replication, an active-active configuration allows multiple group members to accept concurrent write transactions. These writes are coordinated through a consensus-based group communication system (GCS) and validated via write-set certification to preserve global transactional consistency as defined by the Group Replication protocol. active-active mode is designed for write scalability. […]
The post Active-Active MySQL Group Replication Best Practices appeared first on Severalnines.
A New Era of MySQL Community Engagement: Public Community Roadmap Webinar Highlights
Oracle values the MySQL community. MySQL is fundamental to our data strategy. Oracle firmly believes that MySQL’s enduring strength arises from this vibrant global community. We are excited to work with the MySQL Community on the strategy we announced in Belgium, January 29, 2026, including adding more features and functionality, accelerating innovation directly in the […]
I Built an AI That Impersonates Me on Slack, and It Was Disturbingly Easy
I spend a lot of time in Slack. Most people in tech do. It’s where a lot of “work” happens such as quick questions, async decisions, the “hey can you look at this?” threads that never seem to end. It feels personal. You think you know who’s on the other end.
A Practical Approach to Running MySQL HeatWave AutoML in Mission-Critical Environment
MySQL HeatWave AutoML is a native automated machine learning engine tightly integrated with the MySQL HeatWave database. It enables model training, inference, scoring, and explainability through SQL, executing directly on data in InnoDB tables or in external accessed via HeatWave Lakehouse from Object Storage. By operating in-database and in-memory on HeatWave nodes, AutoML eliminates data […]
Mind the InnoDB Purge on Queue / Row Deletion Job (else slow queries)
I am starting a blog post series on using indexes — or tables — as queues. I had this series in the back of my mind for some time. This started a few years back when I worked on optimizing a row deletion job (I do not call this a purge job, to avoid confusion with the InnoDB Purge). Such jobs can be generalized to using indexes (or tables) as queues (this is
Row Deletion Jobs Done Right
I am continuing my blog post series on using indexes — or tables — as queues. In this post, I cover Row Deletion Jobs (I do not call these purge jobs, to avoid confusion with the InnoDB Purge). Such jobs are tempting to implement using an index, but this might be a wrong / suboptimal way. I write about the right / better / cheaper way