MySQL news and engineering summaries

A persistent MySQL bug, identified in 2005, caused triggers to fail during cascading foreign key operations. After 20 years of community discussion and controversy regarding database integrity, the issue has finally been resolved as part of WL#17024, enabling triggers on referenced tables during cascade events.

The article strongly advocates for migrating from MySQL to MariaDB due to the deteriorating state of the former under Oracle's stewardship. By 2026, MySQL showed significant declines in git commits, limited bug tracking transparency, and a shift toward closed-door development. The author highlights technical regressions, performance degradation in newer versions, and a lack of new features in long-term support releases like MySQL 8.4. In contrast, MariaDB maintains a transparent, community-driven development model. Security concerns are also emphasized, noting that MySQL published significantly more CVEs with less disclosure compared to MariaDB. For users seeking to maintain software sovereignty and better performance, the author recommends MariaDB as a compatible, truly open-source alternative that provides an easy migration path for classic LAMP stacks and custom applications.

A software company successfully migrated from DigitalOcean to Hetzner, reducing monthly costs from $1,432 to $233 while increasing performance. By leveraging MySQL master-slave replication and scripting administrative tasks, the migration involved 248 GB of data and 34 Nginx sites with zero downtime, highlighting the cost-efficiency of dedicated servers for stable workloads.

Shopify replaced its Redis-based inventory reservation system with a MySQL-powered solution using SKIP LOCKED. By optimizing index design, transactional isolation, and connection management, they eliminated overselling risks while maintaining high-throughput concurrency during peak sales. The transition leveraged shadow mode monitoring to ensure scalability and ACID compliance across critical checkout operations.

Database freezes in a Galera environment were traced to excessive InnoDB history growth caused by AWS Lambda connection pooling. Idle persistent connections kept transactions open, preventing row version purging. Changing the transaction isolation level to READ-COMMITTED resolved the issue by ensuring short-lived read views and allowing consistent garbage collection of undo logs.

AliSQL is Alibaba's specialized open-source branch of MySQL, specifically forked and optimized for massive-scale production environments. The latest release, version 8.0.44 (LTS), introduces significant enhancements including the native integration of DuckDB as a storage engine, which provides users with lightweight analytical capabilities using standard SQL interfaces. Furthermore, AliSQL now supports enterprise-grade vector storage with up to 16,383 dimensions, utilizing an optimized HNSW algorithm for high-performance Approximate Nearest Neighbor search, making it a powerful tool for AI-driven applications like semantic search. The project roadmap includes ambitious improvements to DDL efficiency, recovery time objectives (RTO), and replication throughput via parallel processing. These features aim to reduce latency and eliminate replication lag, ensuring high availability and stability for modern, data-intensive organizations.

Oracle's Orasort algorithm, which boosts database sorting speeds by comparing 8-byte segments as 64-bit integers instead of character-by-character, has entered the public domain following its 20-year patent expiration. This efficient method reduces CPU cycle consumption, now enabling open-source databases like MySQL and PostgreSQL to optimize performance and lower operational costs in cloud environments.

sql-tap is a real-time SQL traffic viewer composed of a proxy daemon and a TUI client. It intercepts PostgreSQL or MySQL queries using wire protocols to display transactions and performance metrics. Users can run EXPLAIN, analyze execution times, and inspect queries without modifying application code, streaming data via gRPC to an interactive terminal.

Cloudflare made Hyperdrive’s MySQL support generally available after fixing reliability issues, including a rare caching bug that caused empty query results or hangs. Hyperdrive’s Client and Endpoint could share a CDN cache while encoding MySQL responses for different negotiated capabilities, especially CLIENT_DEPRECATE_EOF; either node could read bytes in the other’s format. Cloudflare fixed this by storing canonical result bytes encoded with Hyperdrive’s capabilities, eliminating the empty-row issue and raising Client connection success to 99.99%. It also corrected UTF-8 handling with utf8mb4.

Scaling relational databases to handle millions of queries and petabytes of data requires database sharding. By distributing data and queries across multiple servers, sharding overcomes bottlenecks like write limits and backup constraints. Using proxies and routers like Neki and Vitess, complex sharded architectures can be abstracted to appear as a single, performant unit to applications.

PlanetScale optimizes database backups for sharded Postgres and MySQL environments using massive parallelism. By spinning up temporary nodes per shard to restore backups from object storage and replaying WAL or binary logs, they achieve high-speed, consistent backups with minimal production impact. This infrastructure supports scaling, resizing, and rapid node replacement for petabyte-scale databases.

libeatmydata is an LD_PRELOAD library that disables fsync and similar operations, significantly accelerating disk-writing software. While it improves performance, it makes applications non-crash-safe, risking data integrity. It is primarily used on Linux to speed up tasks like database testing, such as running mysql-test-run, where it can drastically reduce execution time.