1 views collected around this technical thread.
This article introduces and compares three MySQL online schema‑change solutions—pt‑online‑schema‑change, gh‑ost, and native MySQL ONLINE DDL—detailing their workflows, limitations, risks, monitoring features, and practical considerations for safely altering large tables in production environments.
This article documents a real‑world incident where a MyISAM table in a Percona XtraDB Cluster caused data inconsistency and node self‑shutdown, analyzes the root cause, and describes how using pt-online-schema-change together with proper engine conversion restored consistency across the cluster.
A GitHub engineer argues that database foreign keys should be avoided because they shift integrity responsibilities to the DB, incur performance overhead, and cause complications during online schema migrations, illustrating the points with parent‑child tables, gh‑ost, and pt‑online‑schema‑change tools.
This article explains the three MySQL DDL algorithms (COPY, INPLACE, INSTANT), compares third‑party tools like pt‑online‑schema‑change and gh‑ost, and provides practical guidance on selecting algorithms, using ALGORITHM clauses, monitoring progress, and handling performance, space, replication lag, and metadata lock issues.