Adding a new column to a live database is never just syntax. It is change at the core. Rows will swell. Queries will shift. Indexes may break. If the migration is careless, the system stalls and users wait.
The safest path begins with understanding the load. Check table size. Count rows. Review foreign keys and indexes. Adding a column locks different databases in different ways. Some engines lock writes; some lock both reads and writes. Know what yours does before you run ALTER TABLE.
In MySQL and MariaDB, adding a new column to a large table can block traffic for seconds or hours. Use instant DDL when possible. In PostgreSQL, adding a nullable column with a default value will rewrite the table unless you add it without a default first, then backfill in batches. In SQLite, adding a column is usually faster but still deserves care.
Type choice matters. Choosing INT over BIGINT shrinks storage. Choosing JSONB over TEXT shifts how queries run and indexes are built. Plan for how the column will be used, not just how it will be stored.