I guess I gotta do everything twice these days. I shouldn't have been too hasty to deploy #814, since changing a column to NOT NULL in Postgres locks the entire table for reads and writes. This took down production for a few minutes until I could kill the locking queries and revert things. This new PR follows recommendations in strong_migrations.
I guess I gotta do everything twice these days. I shouldn't have been too hasty to deploy #814, since changing a column to
NOT NULL
in Postgres locks the entire table for reads and writes. This took down production for a few minutes until I could kill the locking queries and revert things. This new PR follows recommendations instrong_migrations
.