Issue with Prisma when connection pool enabled

Cloud Integrations Prisma
1

Hi,

I’m trying to run my app presently deployed on Vercel with supabase backend to Neon. But faced following error during build.

prepared statement "s0" already exists when connecting

I can see similar issue reported on other platform

is there any parameter I need to pass for connection string when using pooling?

1 Like
2

Do you have ?pgbouncer=true added to your Prisma database connection url? This is the error that occurs when you don’t.

@ neon team - this would be ideal to add to the Prisma guide at Connect from Prisma to Neon — Neon Docs

3

I also would recommend this article: PgBouncer FAQ

It is said that prepared statements must be disabled because PgBouncer doesn’t track them alone.

4

Thank you adding pgbouncer=true to the connection string seems solved the issue. Thanks for the comments
Thank you Neon Team for the great product, really happy so far…

1 Like