pgbounder=true + prisma
Is pgbouncer=true needed when used with prisma? I saw recent changelog that maybe its not required from neon side (https://neon.tech/docs/changelog/2024-02-23-console), but doesnt prisma use this part of database url string to determine how to execute certain queries/close connections?
2 Replies
unwilling-turquoise•2y ago
@Mahmoud is our Prisma pro, but yes I believe Prisma does use the query parameter to alter its behaviour. PgBouncer has been updated to support Postgres functions prisma depended on, and Neon is running that updated version of PgBouncer. That's why you should be OK without the query param: https://github.com/prisma/prisma/issues/21531#issuecomment-1919059472
GitHub
Fully support prepared statements with pgbouncer 1.21.0 · Issue #21...
Problem Today, the way prepared statements are supported with pgbouncer is suboptimal. Prisma will clear all prepared statements in the connection to avoid mismatches. Now that pgbouncer supports p...
equal-aquaOP•2y ago
gotcha. alright, this is not the answer to my mystery then. @Mahmoud if you ever get some chance to into my issue with neon + prisma + vercel + remix (in general channel https://discord.com/channels/1176467419317940276/1176467419938701375/1229475061161791528 or in zendesk (filled supp ticket)), would appreciate. I’ve wasted so much time on this already, its super critical and I truly see no end to this 😮💨
also, why vercel postgres + prisma (which they host at neon) can work without neon adapter, while hosting directly at neon does need the adapter? (trying to find other clues what might be impacting us)