This week, we're highlighting ProxySQL. As applications grow, so do the demands on MySQL. ProxySQL helps developers and DBAs manage database traffic through connection pooling, query routing, and load balancing, providing greater control over how applications connect to MySQL.
The latest from the MySQL community
Ideas, releases, practical guides, and perspectives from the people building with MySQL.
High-concurrency database workloads rarely fail because of simple CPU or disk capacity limits. Instead, performance collapses occur when transactions serialize on shared internal database resources: metadata locks, data dictionary latches, group communication certification queues, and network buffers.
When contention occurs, external monitoring dashboards often show deceptive metrics such as near-zero CPU and disk activity alongside a massive surge in active connections and application timeouts. MySQL exposes these internal contention points through Performance Schema wait events.
This article—the first in a four-part deep dive—covers the foundational mechanics of Performance Schema wait telemetry, the governance of instrumentation overhead in high-throughput environments, and the diagnosis of Critical System Blocks: Metadata Locks (MDL), Data Dictionary latch serialization, and Group Replication Flow-Control stalls.
…
[Read more]MySQL and DuckDB
Unlike row-oriented databases, which store data for a single record sequentially on disk, favoring single-row lookups, columnar databases store all the values from a column contiguously in storage, allowing only the selected column to be read from disk.
The default MySQL engine is InnoDB, which is ACID-compliant and great for OLTP (Online Transaction Processing) workloads. That said, OLAP (Online Analytical Processing) queries are built differently; they scan, group, and summarize millions or billions of rows to produce reports. In these cases, the InnoDB engine can be slow to process such queries. This has been a debt in MySQL over the years; it was common to setup ETL/CDC pipelines to export or stream the data to another engine, usually a columnar database system, to run reporting and BI queries on it.
DuckDB is a portable analytical database system, designed to be fast and reliable, similar to SQLite. …
[Read more]Welcome back to Village News, our curated roundup of MySQL and database news. This week, AWS contributed a fix for large-transaction binlog stalls to community MySQL, and MariaDB launched Enterprise Platform 2027.
If you want to get these updates, just subscribe to the blog.
Enjoy!
MySQL News
Note: Aggregated MySQL news can be found at Planet for MySQL Community and Planet MySQL (Oracle curated)
AWS contributes a large-transaction binary log
optimization to MySQL
AWS Database Blog
TL;DR …
[Read more]Jonathan shares how he discovered MySQL through building websites and WordPress, his experience at the EU Summit for the MySQL Community, and the challenges of balancing backwards compatibility with modern MySQL features.
MySQL's null-safe equality operator helps you write SQL queries that correctly match NULL values and retrieve records that ordinary equality comparisons miss. See how to filter assigned and unassigned support tickets using null-safe comparisons, and explore the operator's syntax and behavior in the MySQL Reference Manual: https://dev.mysql.com/doc/refman/9.7/...
Learn how the MySQL null-safe equality operator handles NULL values in SQL queries and helps retrieve records that standard equality comparisons can miss. This demo explains the difference between ordinary equality (=) and null-safe equality, showing how each operator evaluates NULL values and affects query results.
Vinicius shares how he got started with MySQL, the community members who inspire him, and his enthusiasm for performance troubleshooting, community events, and AI.
One ecosystem, many projects, shared challenges. Join us in Brussels on Sunday, January 31, 2027, for the M-Ecosystem Devroom at FOSDEM!
Building on the tradition of the MariaDB, MySQL & Friends Devroom, this new chapter expands its scope and ambition, bringing together developers and contributors from across the open-source database ecosystem to share knowledge, tackle common challenges, and foster collaboration across projects.
I shared a meme on LinkedIn because it made me laugh. Then I kept looking at the constraint name at the bottom.
PK__LAW__3214EC07B14E510A.
I would like to cooperate, officer, but I may need a minute to figure out what I did.
PK gives me a clue that this is a primary key constraint. LAW suggests the table involved. The rest gives me something to copy into a search box. A name such as pk_law_id would give me a much better starting point for understanding the violation.
That is a lot to ask of a meme, but it gets at something I care about when I build databases and write code: names should help the person reading them understand what is happening.
A recent post on the MariaDB Foundation Blog has the impressive title How MariaDB 11.8 became about 3× faster on some in-memory workloads, fixing a regression dating back to 10.5. The claim is technically correct when viewed in isolation, but I believe it becomes misleading when the broader context is taken into account. The details are below.
The post mentions a benchmark on 11.8