database-migrations

Zero-downtime database migrations in PostgreSQL use the expand-contract pattern to apply schema changes without locking tables. This approach separates schema deployment from application updates, allowing seamless production updates with minimal service disruption.

The expand-contract pattern for database schema changes splits migrations into expand and contract phases to avoid downtime. It allows new schema versions to coexist temporarily with old ones, ensuring safe production deployments without breaking running applications.

Adding a non-blocking index to a large PostgreSQL table requires using concurrent index creation strategies to avoid locking. This Skill provides specific scripts and guidelines to implement non-blocking index additions safely during production deployments.

Yes, you need to plan data migrations separately from schema migrations to ensure safe execution. This Skill helps define when and how to run each type across different databases, minimizing downtime and errors during complex deployment workflows.

Database migration rollbacks require predefined reverse scripts and careful state tracking to safely revert schema changes. This Skill covers rollback strategies as part of its schema evolution guidelines, ensuring failed deployments can be recovered without data loss.

Yes, these migration strategies extend beyond PostgreSQL to support schema changes across multiple database systems. The guidelines cover general best practices for schema evolution and index management adaptable to various database platforms.