FATAL: too many connections for role "x"
The role reached its per-role CONNECTION LIMIT (often set by hosting providers or free tiers).
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 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.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026