Rank, 14 days: 1 on the Drizzle sheet
5 people reported
All time, since Jul 16.
Pooled transaction() leaks the pool client when BEGIN fails
“Repeated failures can exhaust the local pool.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/drizzle/issues/4956/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Pooled transaction() leaks the pool client when BEGIN fails. BEGIN runs before the try/finally that calls release(), so pool.connect() eventually hangs on an exhausted pool.
Is this your bug?
File my report- Where
- node-postgres session
- Error text
Connection terminated unexpectedlythrow error;Pasted in 3 reports} catch (error) {Pasted in 3 reports- Versions
- 0.45.2 to 1.0.0-rc.4
- How bad
- Stops work: a core feature can't be used.
Original reports5, newest first
- node-postgres transaction() never releases the pool client when begin fails#6633
- node-postgres: transaction() runs BEGIN before try/finally, leaking the pool client when BEGIN fails#6341
- Pooled transaction() leaks the pool client when BEGIN fails (node-postgres / neon-serverless / vercel-postgres)#6241
- node-postgres transaction() leaks the client on a rejected BEGIN and returns broken clients to the pool#6114
- node-postgres pool client is not released when transaction BEGIN rejects#6023