"Too many connections" and connection limits

Each plan allows a set number of connections (22, 47 or 97). Use a connection pool in your app or move up a plan.

Updated November 17, 2026 · 1 min read · Managed Postgres: Troubleshooting

Limits per plan

PlanConnections
1 GB22
2 GB47
4 GB97

The error

too many connections or remaining connection slots are reserved means every connection is in use.

Fixes

  • Use a connection pool in your app and keep it small (for example 5 to 10 per app server). Most frameworks have a setting for it.
  • Close idle connections: long-running scripts and open GUI tools hold connections too.
  • See who's connected: SELECT usename, application_name, client_addr, state FROM pg_stat_activity;
  • Move to a bigger plan if you really need more: Move to a bigger plan.
Was this article helpful?

Still need help?

Our team answers every request, usually within a few hours.

Contact Support

We use cookies to enhance your experience, provide live chat support, and analyze site traffic. By clicking "Accept", you consent to our use of cookies.

Cookie Policy
Accept