October 5, 2026 · QueryKings
Most MySQL fleets still replicate on binlog file and position. GTIDs are a prerequisite for sane failover, for RDS and Aurora cutovers, and for the 8.4 tooling you will meet soon. Here is the online enablement sequence, state by state, plus the statements it outlaws and the errant-transaction trap waiting at the end.
Read moreSeptember 15, 2026 · QueryKings
A backup you have never restored is a hypothesis. How to pick between logical dumps, physical snapshots and clones, keep a binlog chain that actually supports point-in-time recovery, and run a timed drill that produces a real RTO number instead of a policy document.
Read moreSeptember 14, 2026
A join predicate with two different collations silently stops using the index. Here is how utf8mb3, utf8mb4_general_ci and utf8mb4_0900_ai_ci end up mixed in one schema, how to find every mismatch before it costs you a table scan, and how to migrate large tables without a maintenance window.
Read moreSeptember 14, 2026
A platform move is a replication problem, not a dump-and-load problem. How to seed the target, run it as a replica of production, decide between RDS MySQL and Aurora, use Blue/Green where it fits, and cut over with a write pause measured in seconds and a rollback you have tested.
Read moreSeptember 10, 2026 · QueryKings
8.0 leaves premier support in April 2026, and 8.4 is the LTS that replaces it. The version model, the direct upgrade path, the defaults that change under you (authentication, semi-sync, parallel replication), and a cutover plan with a real rollback.
Read moreJune 23, 2026
No downgrade path, a changed default collation, new reserved words, auth-plugin mismatches, and optimizer regressions — the checklist we run before any 5.7-to-8.0 cutover, and the replica-based shape of a safe one.
Read more