Adding a new column is not a trivial schema change. It touches storage, indexing, queries, and application logic. In relational databases, a new column can be persistent, computed, nullable, not null, or tied to default values. Each choice carries trade‑offs in speed, memory, flexibility, and integrity.
When you add a new column to a production table, you change not only the table definition but also how the database engine reads and writes every row. On large datasets, this can trigger full table rewrites or lock contention. In systems with high write volumes, this can spike latency. Choosing the right migration strategy matters.
For synchronous migrations, you may block writes until the schema update finishes. For online migrations, tools and database features let you add a new column without downtime, but these can have hidden replication lag or index rebuild costs. Always benchmark in a staging environment with realistic loads before touching production.