Neon
Performance
Stability
max pool size > 10 in serverless context
Part of the Connection pooling check · fix arrives as a guide
What it is
A connection pool in a serverless context is configured with a max above 10.
Why it matters
The ceiling is per instance, and serverless runs many instances. A max of 20 across 50 concurrent instances is a thousand connections against a limit far below that.
How to fix it
Set max low — 1 to 5 for serverless — and let the Neon pooler handle multiplexing. The instance only serves one request at a time, so a large local pool buys nothing.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.