Planet MySQL HA Blog
The Planet MySQL HA Blog aggregates content from sources that cover topics related to high availability (HA) for MySQL databases.
Continuing the Conversation: MySQL Community Engagement Across JAPAC
One of the key themes of the MySQL Community over the past year has been increasing transparency, participation, and collaboration. Through Public Discussions, Design Proposals, the MySQL Developer Guide, GitHub collaboration, and the MySQL Contributor Summit, we have been working to create more opportunities for the community to engage with the future direction of MySQL. […]
Join MySQL Public Discussion #5: Community Participation, Governance, and Next Steps
As part of our ongoing MySQL Community engagement series, we are pleased to invite you to Public Discussion #5, taking place on July 15, 2026, at 7:00 AM PT. Over the past several months, these public discussions have helped us continue the conversation around MySQL Community Edition, roadmap transparency, contribution paths, GitHub collaboration, and ways […]
Why PostgreSQL needs an AI usage policy
We often hear that open source is about people.
From JSON by Hand to a Guided MySQL Enterprise Edition Audit Filter Wizard
MySQL Enterprise Edition includes powerful audit filtering capabilities, but writing audit filter JSON by hand can be tedious and error-prone. The JSON model is flexible, which is exactly what makes it useful, but it also means that a small typo, a missing event class, or an incorrectly assigned user can change what does or does […]
The Next Phase of MySQL Community Engagement: Accelerating Participation and Collaboration
For over 30 years, MySQL has grown through the contributions, feedback, and collaboration of a global community of developers, database administrators, customers, partners, educators, and open source advocates. That community has helped make MySQL one of the world’s most widely used open source databases. As the ecosystem continues to grow and evolve, so do the opportunities for collaboration. Over the past year, we have […]
Create Replica DB system Made Easy for MySQL HeatWave Service on OCI
MySQL HeatWave Service (MHS) on Oracle Cloud Infrastructure (OCI) already provides multiple ways to create a new DB system, such as restoring from a backup, using Point-in-Time Recovery (PITR), or importing data from Object Storage. However, when creating a new DB system from an existing DB system, especially in another region, the process required several sequential […]
Do not uselessly grant CREATE and ALTER TABLE
This lesson should have been learned with the CREATE TABLE of death, but it is worth a refresh.
Do not uselessly grant CREATE and ALTER TABLE
The reason I am posting this reminder is that another crashing bug related to DDL came to my attention. This bug is only fixed in a recent version of MySQL (probably not affecting 5.6 and 5.7), so if you are running the latest 8.0 or 8.4, you should
MySQL 9.7 – Thank you for your contributions!
On April 21st, 2026, we released MySQL 9.7.0, the latest Long-Term Support release. As always, we are grateful to the MySQL community for helping improve MySQL with bug reports, patches, pull requests, and continued feedback. Community contributions help make MySQL better for everyone, and we are happy to recognize the contributors whose work was included […]
A More Predictable MySQL Release Model: Calendar Versions, LTS, and Innovation
Understanding the New Cadence: Quarterly CPUs, Targeted CSPUs, and Transitioning to Calendar Versioning MySQL is updating its release model to make releases easier to understand, plan for, and follow: The goal is not simply to change the number on a release. The goal is to give users, DBAs, developers, Linux distributions, cloud platforms, and ecosystem […]
Stop Guessing Your Kubernetes MySQL Configs: Meet the MySQL Operator Calculator
Let’s be honest: migrating a relational database to Kubernetes sounds fantastic in a whiteboard meeting, but the reality of day-two operations is a completely different story.
When moving MySQL to Kubernetes, the ultimate goal is simple: identify a safe, performant set of configuration values for your database pods. But where do you start? Usually, you look at your overall node resources say, a machine with 16 CPUs and 64GB of RAM.
In the old bare-metal days, you'd apply the standard rules of thumb:
-
Set innodb_buffer_pool_size to 60-80% of total RAM to…