MyDumper Locking Mechanisms Revisited: Introducing SAFE_NO_LOCK

Running DuckDB as a MySQL 9.7 storage engine

An experimental MySQL 9.7 build called ducksdb-mysql-engine integrates DuckDB as a pluggable storage engine, allowing tables marked ENGINE=DuckDB to offload analytical queries to DuckDB's columnar engine while keeping the same MySQL connection and data. A custom pushdown_select hook (handlerton::pushdown_select) translates qualifying SQL to DuckDB SQL transparently, falling back to the normal row path when needed. TPC-H benchmarks at scale factor 10 show InnoDB timing out on 6 of 22 queries and taking 1317 seconds on the rest, while the DuckDB engine completes all 22 in ~15 seconds. At SF100 (600M rows), the engine remains correct on all 22 queries and stays close to native DuckDB performance, outperforming MariaDB's DuckDB integration on several heavy joins and loading data ~4x faster. The project is open source under GPLv2 and explicitly experimental.

MySQL Community Server 26.7 Early Access Release

MySQL 26.7 Early Access is the first Innovation release after MySQL 9.7 LTS, adopting a CalVer yy.mm versioning scheme. Key highlights include: more robust InnoDB undo log truncation using a header flag instead of a local file; internal InnoDB recovery and metadata infrastructure improvements (redo log, tablespace, MVCC/ReadView interfaces); a new Change Stream Applier for parallel replication with separate apply and commit progression, configurable via APPLIER_VERSION=2; Group Replication now defaults to the MYSQL communication stack with deprecation warnings for XCom options; post-quantum cryptography support (ML-KEM hybrid and pure algorithms) when built with OpenSSL 3.5+; upgrade/compatibility check progress reporting; and the Thread Pool Plugin now available in Community Server. The release is for evaluation only and not intended for production use.

[RFC] [Discussion] Minimum supported versions for PHP 8.6

A PHP internals RFC discussion proposes minimum supported version requirements for PHP 8.6, specifically requiring autoconf for source builds and MySQL 5.7.3 or MariaDB 10.2.4 for persistent connections. The change is tied to adding COM_RESET_CONNECTION support to PDO and mysqlnd, which makes persistent connection behavior more predictable. During discussion, a community member discovered a connection leak when using PDO::ATTR_PERSISTENT with older MySQL versions (5.5.x) against the proposed implementation — each request opened a new connection instead of reusing the persistent one. The RFC author confirmed the leak exists but considers it a bug in the implementation rather than a flaw in the RFC itself.

Percona Operator for MySQL 1.2.0: Cross-Site Replication, Encrypted Backups, and Automatic Storage Scaling

Percona Operator for MySQL 1.2.0 introduces three major features for production MySQL fleets on Kubernetes. Cross-site replication via a new PerconaServerMySQLClusterSet custom resource enables declarative InnoDB ClusterSet topologies spanning multiple clusters or regions, replacing hand-wired async replication. Encrypted backups use XtraBackup's xbcrypt component with keys stored in Kubernetes Secrets, supporting S3, GCS, and Azure targets. Automatic PVC storage scaling monitors disk usage and grows volumes when a configurable threshold is crossed, up to a defined ceiling, eliminating manual intervention. Additional day-two operation improvements are also included.

Release v2.0.0

Mycli v2.0.0 is a major release of the MySQL command-line client with breaking changes. New features include fuzzy history search via fzf, integrated LLM support via a /llm command, shell-like query-result redirection operators, system keyring password storage, improved batch execution with checkpoint/resume and progress/ETA, enhanced auto-completion leveraging foreign keys, fuzzy completion/correction via RapidFuzz, and SSL modernization.

[RFC] [Discussion] Minimum supported versions for PHP 8.6

An RFC has been proposed for PHP 8.6 that introduces minimum supported version requirements: a minimum autoconf version for building PHP from source, and minimum database versions of MySQL 5.7.3 and MariaDB 10.2.4 when using persistent connections. The proposal is tied to adding COM_RESET_CONNECTION support to PDO and mysqlnd, which requires these minimum database versions to function correctly.

InnoDB Flushing is simple – explained

Bài viết giải thích cơ chế flushing trong InnoDB theo cách dễ hiểu cho người mới, bao gồm bốn loại flushing: background, adaptive, LRU và sync flushing. Nó cũng đề cập đến các khái niệm như dirty pages, checkpoint age và redo log thông qua những ví dụ tương tự đời thường, đồng thời cung cấp ba lệnh chẩn đoán thực tế để phát hiện vấn đề flushing. Ngoài ra, bài viết còn đưa ra các giải pháp cụ thể như điều chỉnh dung lượng redo log, tối ưu IO capacity và kích thước buffer pool.

Lập trình viên cần hiểu cơ chế flush của InnoDB để tối ưu hóa hiệu suất cơ sở dữ liệu, tránh tình trạng lag do log đỏ (redo log) và bộ nhớ cache không được quản lý hiệu quả, đặc biệt khi xây dựng ứng dụng yêu cầu độ tin cậy cao.