A single schema change can decide the speed of your next release. Adding a new column is simple on paper, but in production environments it can be the point where deployments stall, data breaks, or performance drops.
A new column in a relational database means altering the structure of a table. Behind that command, the database may rebuild storage, lock writes, or trigger migrations that hit every row. In large datasets, this operation can be expensive. The right approach depends on your RDBMS, the size of your tables, and the nature of the field you are adding.
For PostgreSQL, adding a nullable column with no default is fast—it updates metadata only. But a new column with a default value will rewrite the entire table unless you use a later version that applies defaults lazily. MySQL behaves differently; some operations run instantly for certain data types and storage engines, others are blocking. In both systems, careful planning around indexes, constraints, and triggers is essential to avoid locking your application.