Adding a column to a tens‑of‑millions‑row MySQL table may look trivial, but the real difficulty lies in the metadata‑lock timing and online traffic impact, requiring careful DDL type selection, pre‑flight checks, and often an online migration tool such as gh‑ost to avoid business‑level outages.
The article explains how to safely add indexes to a tens‑of‑millions‑row MySQL table, covering lock duration, disk‑space impact, write‑performance degradation, and six practical principles—selective columns, proper order, covering indexes, avoiding redundancy, short‑lock tools, and ongoing monitoring—plus pros, cons, and suitable use cases.
This guide explains why using a plain ALTER TABLE on massive MySQL tables can lock the table and halt services, and presents tool‑based online DDL, native INPLACE options, phased migration strategies, cloud‑DB features, best‑practice checks, monitoring, and rollback techniques to add new columns safely.
This article explores why adding columns to massive MySQL tables can lock the database, explains the risks, and presents six practical solutions—including native online DDL, downtime maintenance, PT‑OSC, logical migration with dual writes, gh‑ost, and partition sliding windows—along with best‑practice tips for monitoring, backup, and performance.
This article presents a detailed case study where the ChatDBA AI assistant diagnoses and resolves a gh-ost migration stall caused by large table size and VARCHAR length expansion, compares its response with DeepSeek, and showcases the tool's expert-mode root‑cause analysis and actionable recommendations.
This article recounts the development of ZzoOnlineDDL, a MySQL schema‑change platform, detailing its 1.0 limitations, the 2.0 architectural upgrades, feature set—including intelligent tool selection, timed execution, sharding support, monitoring, and retry mechanisms—and lessons learned from real‑world incidents such as MDL locks, disk pressure, and unique‑index pitfalls.
While MySQL 5.7 native DDL methods (copy, inplace rebuild, index build, metadata‑only) vary in speed, space use, lock impact, and binlog output, GH‑OST consistently offers the fastest execution, lowest lock blocking, real‑time replication, albeit at roughly double storage cost, making it ideal for risk‑averse online schema changes.
This article details a step‑by‑step strategy for expanding a VARCHAR column from 50 to 500 characters on a 4‑hundred‑million‑row MySQL 8.0 table, evaluating online DDL, gh‑ost, pt‑osc, and ultimately implementing a cascade replication workflow to meet a four‑hour downtime window.
This article explains how to add unique indexes to large MySQL tables using Online DDL, pt‑osc, and gh‑ost, compares their advantages and drawbacks, outlines common data‑loss risks, and provides practical hook scripts and best‑practice recommendations to mitigate those risks.
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.
The preview release SQLE 1.2205.0-pre2 introduces LDAP over SSL support, stricter error handling for gh‑ost dry‑run failures, several bug fixes, and provides updated documentation and download links for the open‑source SQL audit platform.
The SQLE 1.2204.0 release introduces an optimized SQL deployment workflow with approval steps, gh-ost dry‑run enhancements, real‑time message push for audit results, expanded permission controls, and a comprehensive list of new features, improvements, and bug fixes.
This article documents a reproducible test that shows gh-ost can lose rows when used on a MySQL 5.7 AFTER_SYNC semi‑synchronous replica, explains the underlying cause, and presents a source‑code modification that prevents the loss.
This article examines the pain points of MySQL DDL operations for large tables, analyzes the limitations of online DDL, compares tools like gh‑ost and pt‑osc, and outlines a comprehensive workflow and implementation details for an automated online DDL work‑order system.
This article details the design, evolution, and operational practices of Ctrip's MySQL database release system, covering its three major versions, the adoption of gh‑ost, safety mechanisms, real‑world case studies, and performance improvements that enable reliable, low‑impact schema changes at scale.
This article provides a comprehensive guide to gh-ost, the GitHub‑released online MySQL schema migration tool, covering its design principles, three migration modes, download and RPM installation, common command‑line options, interactive socket commands, and a step‑by‑step example of altering a column type while monitoring progress and performing a safe cut‑over.
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 internal workflow of the gh‑ost online DDL tool, covering its execution steps, binlog handling, data consistency analysis, cut‑over process, lock management, and failure scenarios, with detailed code examples and practical insights for safe schema changes in MySQL.
This article introduces the gh-ost tool for performing online schema changes on large MySQL tables, explains its architecture and operation modes, provides detailed command‑line parameters and practical examples, and compares its features and performance with the traditional pt‑osc solution.
This article explains how MySQL performs DDL operations on large tables without long‑lasting locks, covering the evolution from copy‑table and in‑place methods to Fast Index Creation, Online DDL introduced in 5.6, and third‑party tools PT‑OSC and GH‑OST, with detailed process steps and comparisons.
This article explains why MySQL auto‑increment primary keys can reach their limit, shows how switching from INT to BIGINT prevents overflow, and reviews three online schema‑change methods—including native ALTER, pt‑osc, and gh‑ost—plus considerations for triggers, foreign keys, and master‑slave setups.
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.
This article explains the challenges of MySQL DDL on large tables, details the built‑in COPY, INPLACE, and INSTANT algorithms, compares third‑party tools like pt‑online‑schema‑change and gh‑ost, and provides practical guidance on minimizing impact, monitoring progress, and handling metadata locks.
gh‑ost is a lightweight, trigger‑free, Go‑based online MySQL schema‑change tool that reads binary logs, applies alterations to temporary tables, and offers pauseable, auditable, and dynamically controllable migrations via socket commands, supporting master‑only, replica‑assisted, or replica‑testing modes and used extensively at GitHub.
