prisma migrations frequently fail with P1002 timeout
what it says on the tin. what can we do about that?
3 Replies
ratty-blush•14mo ago
I have no first-hand experience, but I do remember this topic being documented in our docs: https://neon.tech/docs/connect/connection-latency and CTRL-F for all prisma occurances.
quickest-silverOP•14mo ago
thanks - this isn't a general connection timeout though, it's specifically the advisory lock
presumably some kind of issue where it's not being released properly
wise-white•14mo ago
https://github.com/prisma/prisma/issues/6768#issuecomment-1728979024 should solve it @Avi
GitHub
Error: P1002 database server was reached but timed out · Issue #676...
Bug description I was running prisma migrate dev and ran into this error. Error: P1002 The database server at
xx.xx.xx.xx:5432 was reached but timed out. Please try again. Please make sure your...