Database Error: remaining connection slots are reserved for non-replication superuser connections #13995
Locked
canumula
announced in
Troubleshooting
Replies: 1 comment
-
|
You can inspect your database’s connections with Supabase's Grafana Dashboard. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This error usually occurs when the database reaches the maximum number of connections allowed based on the compute add-on.
To overcome this, the connections need to be optimized as mentioned here: https://supabase.com/docs/guides/platform/performance#optimizing-the-number-of-connections
Additionally, you can try using the connection pool to help solve this issue:
https://supabase.com/docs/guides/database/connecting-to-postgres#connection-pooler
If you're already using connection pooling and still hitting the maximum connections, then it is suggested to upgrade your compute add-on that allows more connections: https://supabase.com/docs/guides/platform/compute-add-ons
Beta Was this translation helpful? Give feedback.
All reactions