Adding a new column to a database sounds trivial until it breaks production queries, slows batch jobs, or causes silent data loss. Schema changes are one of the most dangerous operations in any system at scale. The pressure grows with every live user and every request per second.
A new column changes the shape of your data, the storage layout, and sometimes the query plan. On small datasets, the change might be instant. On large tables, adding a column with a default value can lock writes for minutes or hours. Even without defaults, an ALTER TABLE may trigger a full table rewrite. Always check what your database does under the hood before running the command.
Plan the change in phases. First, add the new column as nullable. Verify that replication and backups are stable. Backfill data in controlled batches to avoid spikes in I/O and CPU. Update application code to write to both the old and new fields. Once the data is complete, switch reads to the new column. Then, only when you are certain, drop the old field.