Neon
Cost
Performance
Stability
Pool with idleTimeoutMillis: 0 or missing (long-lived process)
Part of the Idle compute cost check · fix arrives as a pull request
What it is
A connection pool in a long-lived process has idleTimeoutMillis set to 0 or left unset, so idle connections are held open indefinitely.
Why it matters
An open connection prevents the compute endpoint from suspending. A single idle pool connection is enough to keep the database billing all night for zero queries.
How to fix it
Set idleTimeoutMillis to something short — 10 to 30 seconds — so the pool releases connections during quiet periods and the endpoint can suspend.
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.