Adding a new column is one of the most common schema changes. It sounds simple, but it can break production if you get it wrong. The operation changes the structure of your table, the way rows are stored, and the way queries return data. In a small dataset, it’s instant. In large systems, it can lock writes, trigger table rewrites, or cause downtime.
Before you run ALTER TABLE ADD COLUMN, confirm the type, default value, and nullability. Avoid large default writes that rewrite the table chunk-by-chunk. For high-traffic systems, add the column as nullable first, backfill in batches, then enforce NOT NULL and defaults later. This pattern reduces lock time and keeps the change online.
Consider index impact. Adding an indexed column means extra storage and slower inserts. If you don’t need it in a query filter, skip the index. If you do, create it after backfill to avoid huge replication lag.