migration-advisor

Zero-downtime database migration uses the expand-contract pattern to apply schema changes without locking production tables. This approach separates changes into backward-compatible phases, allowing new and old application versions to run simultaneously during deployment.

Safely adding a nullable column in PostgreSQL requires issuing an ALTER TABLE statement with a default null value. This avoids table rewrites and long locks, allowing the database to accept the schema change immediately without interrupting ongoing read and write operations.

Prisma supports safe rollback strategies through its migration tooling by allowing you to define and apply reversible SQL schemas. You can manually craft down-migrations to restore previous states, ensuring production deployments remain reversible if unexpected issues occur.

Large data migrations require batch processing and transactional safety to avoid long database locks. By updating data in smaller sequential chunks within individual transactions, you minimize contention and prevent production downtime during extensive data transformations.

Django ORM supports the expand-contract pattern by generating custom migration files that apply backward-compatible schema changes. You deploy additive changes first, update the application layer, and then schedule a subsequent migration to remove deprecated columns.

Creating an index locks your PostgreSQL database because a standard CREATE INDEX operation blocks concurrent writes to the target table. To prevent this, use CREATE INDEX CONCURRENTLY for zero-downtime deployments, allowing writes while the index builds.