Prisma/tRPC query failing 1/2 the time, but only in Prod
So I have an app, in my local dev environment, everything is working as expected in regards to the DB, I do a fetch to my dev DB and I get the data back as expected every time. I just deployed to Vercel, connected to the prod DB(hosted by Supabase), and 1/3 of the time the fetches work fine, 2/3 of the time I'm getting an error from Prisma that the fetch(s) couldn't be completed, "error occurred during query execution". Trying to think about how to approach diagnosing this since I can't reproduce in dev. Any help is appreciated!
![No description](https://cdn.answeroverflow.com/1228390722584051763/Screenshot_2024-04-12_at_9.png)
Solution:Jump to solution
GitHub
prepared statement "s0" already exists · Issue #11643 · prisma/pr...
Bug description I'm connecting to Supabase with their connection pooling enabled and I'm seeing the following 500 errors after multiple refreshes of the same page, until eventually it force...
9 Replies
This is one of the other errors that comes back for w/e reason, not sure this is any more helpful than the first one 😅
![No description](https://cdn.answeroverflow.com/1228391157852274708/Screenshot_2024-04-12_at_10.07.31_AM.png)
Can you show the complete error log?
Solution
GitHub
prepared statement "s0" already exists · Issue #11643 · prisma/pr...
Bug description I'm connecting to Supabase with their connection pooling enabled and I'm seeing the following 500 errors after multiple refreshes of the same page, until eventually it force...
looks like is the same issue
You're a legend
:PotBased:
It's so dumb, in Supabase's Prisma docs, they talk about adding the
?pgbouncer=true&connection_limit=1
but in their Dashboard, when you click the connect button and copy the .env variables they auto generate, it does not include the pgbouncer querry param. Sigh. Gonna report that bug now, thanks nyxglad that fixed the issue