Adding a new column is one of the most common schema changes in modern software. It looks simple. It can bring a system down if you get it wrong. The right approach depends on your database engine, your migration tooling, and your uptime requirements.
In PostgreSQL, an ALTER TABLE ... ADD COLUMN with a default value writes to every row. On a large table, this means a lock and potential downtime. A safer path is to add the column without a default, backfill in controlled batches, and then set the default. MySQL and MariaDB behave differently, but large table alterations can still block access unless you use tools like pt-online-schema-change or native instant DDL when supported.
When adding a new column in a production environment, always measure row count, index state, and lock impact before touching the schema. On critical systems, run the operation in staging with production data volumes. Track replication lag closely. Monitor disk I/O and CPU impact during any backfill jobs.