Timed out trying to acquire a postgres advisory lock

I get this for 4/5 deploys, even when I'm not running a migration. Why is this???

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.

2 Replies

rival-black•4mo ago

Looks like prisma is using advisory locks during schema migration perhaps. It could be that a particular migration step is slow (if you add a new index) which could cause other deploys running the same migration script to wait on the advisor lock I don't know for sure though

flat-fuchsiaOP•4mo ago

Interesting seeing that there aren't any migrations being run

Gaming

Programming

Timed out trying to acquire a postgres advisory lock

Did you find this page helpful?