A new column can be simple or it can be the trapdoor to a long outage. The difference is in how you handle schema changes in live systems. For relational databases, ALTER TABLE ADD COLUMN is straightforward in development but can lock large tables in production. The safest path depends on your database engine, the table size, and how you manage writes during the change.
When adding a new column in PostgreSQL without constraints or defaults, the operation is fast because it updates only the metadata. If you set a DEFAULT on a large table, expect a rewrite. In MySQL, adding a column often triggers a table copy unless you use the newer ALGORITHM=INSTANT option in modern versions. Understanding these details will keep your deployment predictable and prevent downtime.
Plan for the application to be aware of the column before and after the migration. Deploy code that can handle both states. Backfill data in controlled batches. Monitor performance during and after the change. Roll forward, not back.