Skip to content

fix(deploy): tolerate P1002 (migrate advisory lock timeout) #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abdout merged 1 commit into from
May 10, 2026
Merged

fix(deploy): tolerate P1002 (migrate advisory lock timeout) #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions scripts/maybe-migrate.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,21 @@ try {
process.exit(0);
}

// P1002 = "Database server reached but timed out." Most often surfaces
// here as a stuck advisory lock when a previous deploy crashed without
// releasing it, or two deploys race for the same lock. Skipping is
// safe — the next deploy retries, and Prisma's _prisma_migrations
// table prevents double-application.
if (combined.includes("P1002")) {
console.warn(
"\n⚠️ P1002: migration lock timeout — skipping migrate deploy this build.\n" +
" The next successful deploy will retry. If this persists, manually\n" +
" release the advisory lock against production DATABASE_URL:\n" +
" SELECT pg_advisory_unlock(72707369);"
);
process.exit(0);
}

console.error("\n❌ prisma migrate deploy failed:", err.message);
process.exit(1);
}
Loading