Planet MySQL HA Blog
The Planet MySQL HA Blog aggregates content from sources that cover topics related to high availability (HA) for MySQL databases.
MySQL Contributor Summit 2026: Collaboration, Innovation, and Community-Driven Development
On May 26, The MySQL Community Team at Oracle welcomed MySQL contributors, customers, partners, and community members to the MySQL Contributor Summit at the Oracle Redwood Shores campus, with additional participants joining remotely. The Contributor Summit brought Oracle engineers and community contributors together to exchange ideas, share ongoing work, and explore opportunities to collaborate on […]
Opening Up the MySQL Bug Process
The MySQL team has been working hard to foster innovation, strengthen collaboration with our community, support meaningful contributions, and grow the broader MySQL ecosystem through greater openness and transparency. We believe MySQL is at its best when everyone can see how progress is being made, where work is happening, and how issues move through the […]
MySQL 9.7 LTS Is Here: Upgrade and Modernize on a Stronger Community Edition
MySQL 9.7 LTS is here, establishing the new MySQL 9.7.x Long-Term Support release line. For organizations running MySQL today, this is the right time to evaluate upgrade plans and move toward a current, supported foundation. It is also a good moment for teams standardizing their database strategy to take a fresh look at MySQL. Whether […]
No More JSON Plumbing: MySQL 9.7 Community Levels Up Duality Views
Modern applications often pass JSON back and forth with the database server. With MySQL, we have had great JSON support, but working with relational data as JSON usually meant generating documents manually with built-in JSON functions. When an application sent JSON back to the server, we often had to break that document apart and write […]
Inserting in Two Tables in a Single Round-Trip with JSON Duality Views in MySQL 9.7
A few months ago, I was asking myself how to insert in two tables in a single round-trip to the database. I wanted to do that to optimize a process. My optimization involved splitting a table in two, which would need inserting in two tables atomically. The downside was changing an auto-commit INSERT to a transaction with two inserts, which was changing the shape of the workload
Summary of MySQL Public Discussion #4: Updates and Improvements to Contributions – Let’s Talk About What’s Next for MySQL
One of the best things about MySQL has always been its community. Whether you’re building applications, running production databases, contributing code, creating tools, writing documentation, answering questions, or simply sharing feedback, you’ve helped make MySQL what it is today. In this discussion we shared updates on where we are today and had a discussion on […]
From Question to Insight with MySQL Studio
When we introduced MySQL Studio, the goal was to bring the common parts of database development and analysis into one OCI workspace: SQL authoring, schema exploration, results visualization, and Ask Studio. The next step is making that workspace more useful during the everyday flow of MySQL work. For many MySQL developers, DBAs, and application teams, […]
The Percona Community Slack is open — come hang out
The Percona Community Slack is open — come hang out There’s a new place for the people behind the databases to actually talk to each other.
Where can you find MySQL during June–August 2026?
The MySQL Community team will be active across conferences, user group meetups, open source events, and regional community activities during the summer months. Whether you would like to hear about the latest MySQL 9.7 updates, meet the MySQL team, join a user group meetup, or connect with the broader open source and developer community, here […]
Building Smart Semantic Search using PostgreSQL and pgvector. Case Study - Part 2 - Postgres Layer
I’ll explain how I built the Postgres layer for semantic vector search on the Percona Community website: pgvector, chunks, two table modifications, the database schema, how the indexer populates Postgres, and what the SELECT statement looks like during a search.