The latest from the MySQL community

Oracle plans to move MySQL security updates toward a monthly cadence, supplementing the current quarterly Critical Patch Update (CPU) schedule. These monthly Critical Security Patch Update (CSPU) releases will be issued only when needed to address critical security or stability issues; they are not a fixed monthly release commitment. These CSPU releases will focus on […]

VillageSQL Server 0.0.6 is now available. This release advances the mainline to MySQL Server 8.4.11 and adds support for MySQL Server 9.7.2 and Percona Server 8.4.10.

Highlights of this release include the following:

• An extension can now log you in, so your identity provider decides who gets into the database.
• Extensions can call the server's own internal component services, which opens up a large part of the MySQL surface area.
• A privilege of its own now covers extension management, so you can grant that and nothing else.
• If you build a custom type incorrectly, you find out when you compile the extension or when you install it, rather than when someone runs a query.

VillageSQL now runs on MySQL Server 9.7 and Percona Server 8.4

VillageSQL Server 0.0.6 adds a mysql-9.7 build that tracks the MySQL Server 9.7.2 tree, and a percona-8.4 build …

Two recent posts on the Percona blog caught my attention. In Replicating from InnoDB into a DuckDB storage engine and The DuckDB MySQL engine at 500 GB, Evgeniy Patlan wired DuckDB into mysqld as a storage engine, pointed row-based replication at it, and measured it at TPC-H scale factor 500. The numbers are striking: loads 25 times faster than InnoDB, one fifth of the disk, and the full 22-query TPC-H suite done in 186 seconds where InnoDB needed about 28 hours and never finished four of the queries.

The posts are also honest about the cost. The work is experimental. The worst bug found was silent data loss on every replicated transaction: the two-phase commit code for mixed-engine transactions dropped prepared DuckDB transactions …

The MySQL Community team will continue to be active across conferences, user group meetups, open source events, and regional community activities throughout August, September, and October 2026.  While some of our August events were featured in our previous event update, we’ve included them here again with the latest information. Whether you’re interested in learning about MySQL 9.7 LTS, exploring the latest features in […]

MySQL Galera Cluster reaches end of life on September 30, 2026. This guide compares five practical paths forward - MariaDB Galera Cluster, Percona XtraDB Cluster, self-managed MySQL, managed cloud MySQL and Tungsten Cluster - with the trade-offs, migration effort and long-term risks of each.

Tối Ưu Chỉ Mục (Index) Trong MySQL Cho Dev PHP Mới

Tối ưu chỉ mục (index) trong MySQL là kiến thức cơ bản mà nhiều dev PHP mới hay bỏ qua. Có bạn dev mới ra trường nhắn tin kể cho chúng tôi về một buổi tối khá căng thẳng. Ứng dụng quản lý đơn hàng bạn viết chạy mượt suốt mấy tuần thử nghiệm với vài trăm bản ghi. Nhưng khi khách hàng thật bắt đầu dùng, dữ liệu tăng lên vài chục nghìn dòng. Trang danh sách đơn hàng bỗng dưng tải chậm tới mức khách phàn nàn. Bạn kiểm tra code PHP mãi không thấy lỗi gì. Tới khi một anh senior xem qua mới phát hiện câu truy vấn tìm đơn hàng theo mã khách chưa hề có chỉ mục. Điều này khiến MySQL phải quét qua toàn bộ bảng mỗi lần tìm kiếm. Đây là tình huống khá phổ biến ở nhiều dev PHP mới vào nghề. Chỉ mục …

MySQL Galera Cluster maintenance ends September 30, 2026, while MySQL 8.0 has already reached end of life. Learn what these overlapping lifecycle changes mean, what risks increase after support ends, and what teams should decide before the Galera EOL deadline.

The MySQL community gathered once again for the second MySQL Contributor Summit of 2026, held August 5–6 as a hybrid event from Broomfield, Colorado. Building on the momentum of the inaugural summit in May, MySQL contributors from across the MySQL ecosystem came together to share ideas, review technical proposals, and collaborate on the future of MySQL.  Over two […]

Visual Studio 2026 ships SQL projects through SSDT, and only the original project format. Here is how to configure, validate, version, deploy, and drift-check a database project without discovering the gaps during a release.

The post 13 best practices for database development in Visual Studio 2026  appeared first on Devart Blog.

When something goes wrong inside MySQL, the server says so in the error log. It's what administrators already watch. Every entry carries a severity and an error code, and you can query it from performance_schema.error_log like any other table. It is the server's place for communicating "something here needs your attention." This is an example of a service that MySQL provides out of the box. Since 8.0, MySQL's component framework has been able to leverage these services, and now the VillageSQL Extension Framework can too.

VillageSQL is a drop-in replacement for MySQL that lets you run your own code inside the server. The VillageSQL Extension Framework (VEF) gives you a channel to expand MySQL via portable extensions written in C++ or Rust, …