# A Fail-Fast PostgreSQL Migration Preflight for CI | Percona Community **URL:** \ **Category:** Community website\ **Created:** [September 8, 2026, 5:26pm UTC](https://forums.percona.com/t/a-fail-fast-postgresql-migration-preflight-for-ci-percona-community/41252 "2026-09-08T17:26:07Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\ **Post date:** [September 8, 2026, 5:26pm UTC](https://forums.percona.com/t/a-fail-fast-postgresql-migration-preflight-for-ci-percona-community/41252/1 "2026-09-08T17:26:07Z")
A database migration can be syntactically correct and still be a poor release candidate. A regular index build can block writes, an `ALTER TABLE` may wait behind a conflicting lock or hold a strong lock longer than expected, and a large data modification can turn a routine deployment into an incident. * * * This is a companion discussion topic for the original entry at [https://percona.community/blog/2026/09/08/postgresql-migration-preflight-ci/](https://percona.community/blog/2026/09/08/postgresql-migration-preflight-ci/) ---
**Author:** ![isersea](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/isersea/32/24323_2.png) [@isersea](https://forums.percona.com/u/isersea)\ **Post date:** [October 5, 2026, 10:23am UTC](https://forums.percona.com/t/a-fail-fast-postgresql-migration-preflight-for-ci-percona-community/41252/2 "2026-10-05T10:23:10Z")
Spot on, daniil.bazhenov! [🚀](https://destinymatrics.com/your-life-path-number) Database migrations looking fine on paper while causing locks or heavy write-blocking in production is a classic deployment nightmare. Having a solid preflight check in CI/CD for schema changes and heavy locks is an absolute lifesaver. Great read