A rolling deployment can leave old and new application versions running together. An immediate rename or drop can break the old version while the new one starts. Expand the schema first, deploy compatible writes, backfill existing records, switch readers and remove the old representation only after its users are gone.
Backfills should be restartable and bounded. A new nullable column lets you migrate existing rows before enforcing a requirement. A CHECK constraint added NOT VALID can protect new writes while postponing the scan of old rows; VALIDATE CONSTRAINT checks the existing population later. Plan lock duration as well as correctness.
CREATE INDEX CONCURRENTLY has special transaction restrictions and failure states. It is an operational deployment command, not a promise that every DDL statement is lock-free. The browser executes local schema transformations but can't rehearse a fleet-wide zero-downtime deployment or background traffic.
Expansion adds a compatible nullable field before readers depend on it.