FATAL: too many connections for role "x"
The role reached its per-role CONNECTION LIMIT (often set by hosting providers or free tiers).
Exact message you may see
too many connections for role
Seen on:
PostgreSQL
Meaning
Different from max_connections: this cap applies to one role. Free database tiers set small limits.
Common causes
- Role connection limit reached
- Pools too large for the plan
- Leaked connections
⚡ Quick fix
- Reduce pool size
- Use the provider’s pooler
- Raise the role limit if you control it: ALTER ROLE app CONNECTION LIMIT 50
Detailed fix by platform
PostgreSQL
SELECT rolname, rolconnlimit FROM pg_roles WHERE rolname = 'app';
How to diagnose
- Limit — rolconnlimit?
- Usage — count in pg_stat_activity
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in PostgreSQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026