Adding a new column should be simple. In practice, it can break indexes, increase storage costs, and interrupt service if not done right. Schema changes are one of the most sensitive parts of database management, especially in production systems under heavy load.
A new column affects performance. It changes how rows are stored and retrieved. On wide tables, a single extra column can push a row past page boundaries, leading to more I/O. On large datasets, a blocking ALTER TABLE can lock writes for minutes—or hours. You need to choose between immediate changes and background migrations based on your workload and SLA.
Types matter. Adding a nullable column is faster than adding one with a default value, because the database often only updates metadata. Non-null defaults can trigger full table rewrites. Check your database engine’s behavior before making a move—PostgreSQL handles some cases in constant time, while MySQL often requires table copy operations.