Prisma•3mo ago

Advisory lock errors in CI suddenly ocurring very frequently

I have a newish (about 2 months old) next.js app with prisma deployed on Vercel. Lately I'm getting Error: P1002 on about 75% of my builds, even when there are minutes between builds.

Context: Timed out trying to acquire a postgres advisory lock (SELECT pg_advisory_lock(72707369)). Elapsed: 10000ms. See https://pris.ly/d/migrate-advisory-locking for details.

Context: Timed out trying to acquire a postgres advisory lock (SELECT pg_advisory_lock(72707369)). Elapsed: 10000ms. See https://pris.ly/d/migrate-advisory-locking for details.

I understand the advisory lock, and I don't like the idea of flat out disabling it. Is it possible to only attempt to acquire a lock if there are pending migrations? 99% of the time it has no migrations to run.

0 Replies

No replies yetBe the first to reply to this messageJoin

Gaming

Programming

Advisory lock errors in CI suddenly ocurring very frequently