Any suggestions for how to resolve an error like t...
# orm-helpQuestion
How can I resolve a timed out postgres advisory lock error?
Answer
There could be several reasons for this error, including a stuck migrate process or multiple deployments running concurrently. One potential solution is to restart the database server. Additionally, checking the locks in PostgreSQL may provide useful information for resolving the issue.
t
Trenton K
04/21/2022, 8:41 PMAny suggestions for how to resolve an error like 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.n
Nurul
04/22/2022, 3:34 PMHey Trenton 👋
It could be a couple of things:
• There is a migrate process still running somewhere that is holding the lock.
• If you see this error while deploying the app, it probably means there are multiple deployments running concurrently. In that case, the error is expected for all but one of the runners.
t
Trenton K
04/22/2022, 3:44 PMI think it's the first issue. I accidentally quit my terminal before selecting “y/n” for “do you want to proceed with this migration?”
Trenton K
04/22/2022, 3:44 PMIs there a way to resolve this?
n
Nurul
04/26/2022, 10:11 AMIs it possible to restart your database server?
j
Joël
04/26/2022, 5:02 PM
@Trenton K there are some ways to check the locks in PostgreSQL like https://stackoverflow.com/a/26596931/1345244
Might be interesting to check if you find something there
✅ 1
118 Views