Closed ffxsam closed 2 months ago
I'm also experiencing these errors. I'm wondering if it's because I'm using a pooled connection string.
@davidchalifoux I was advised not to use the pooled connection (for now), and to use neonConfig
to set this:
import { neon, neonConfig } from '@neondatabase/serverless';
neonConfig.fetchConnectionCache = true;
@conradludgate Am I right in thinking that the latest pgbouncer is now rolled out in production, and is expected to stop this happening?
I believe that deployment of the latest pgbouncer some time ago should have fixed this. Please reopen if that's not the case.
Steps to reproduce
Unknown (error is sporadic)
Expected result
???
Actual result
Randomly, I'm seeing cryptic errors like this:
Then if I reload our app, it runs just fine (with no code changes).
Environment
Node.js 18.x, Lambda, SST, working locally (SST dev mode)