The database was silent until you added a new column, and then everything changed.
A new column is more than an extra field in a table. It alters queries, indexes, storage, and performance. When you add a column to a production database, you change the shape of the data. That change can speed up development or slow every request. The details decide which outcome you get.
Design the new column with precision. Define the correct data type. Avoid nullability unless it has a purpose. Place the column where it makes sense for the schema, though physical ordering matters mainly for storage engines that store row data contiguously. Consider the indexing strategy before you deploy. Adding an index to a new column can improve lookups but also increase write costs.
Before altering the table, check the size of the dataset. On massive tables, a blocking "ALTER TABLE ADD COLUMN"can lock reads and writes. Use online schema change tools or database-native online DDL for minimal downtime. Test your migration on a copy of production data to discover hidden costs.