database-migration

Safe PostgreSQL migrations require forward scripts paired with rollback scripts to ensure non-destructive schema changes. This skill generates both upgrade and downgrade templates for adding tables, columns, indexes, and data modifications across development, staging, and production environments.

The best way to add a column without downtime is using non-destructive migration patterns. This skill provides templates for adding columns with forward and rollback scripts, ensuring you can safely apply and revert schema changes across development, staging, and production environments.

Yes, this PostgreSQL migration approach works for production environments. It enforces non-destructive practices, requires rollback scripts for every change, and provides testing guidance for copy environments to ensure safe schema changes in development, staging, and production.

To rollback a schema change in PostgreSQL, you need a dedicated downgrade script that reverses the forward migration. This skill enforces non-destructive practices by requiring rollback scripts for all schema changes, including adding tables, columns, indexes, and data migrations.

Yes, you can use this for data migrations and index creation in PostgreSQL. The skill provides migration templates and patterns for modifying data, creating indexes, adding tables and columns, with accompanying rollback scripts and documentation guidance.

Automated PostgreSQL schema changes require careful testing in copy environments before applying to production. This skill enforces non-destructive practices and mandatory rollback scripts, but limitations include the need for thorough testing guidance and clear documentation for complex data migrations.