© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•3y ago•
3 replies
Hoobie

Max connections reached on large traffic

When hit with large traffic on our website, we're getting the error that the max connections have been met for Prisma. "Error querying the database: FATAL: Max client connections reached" Believe this comes from the ENV variable setting connection limit to 1. This is suggested in https://supabase.com/partners/integrations/prisma

I increased the connection limit from 1 to 2, and it seemed to solved the problem. Is this the right thing to do? If not, what should I do instead?
Supabase
Prisma | Works With Supabase
Next-generation Node.js and TypeScript ORM.
Prisma | Works With Supabase
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

"Max client connections reached" on Transaction Pooler
SupabaseSSupabase / help-and-questions
4mo ago
Issues with max client connections reached
SupabaseSSupabase / help-and-questions
7mo ago
Getting "Max client connections reached" with only 25/60 connections
SupabaseSSupabase / help-and-questions
3y ago
Self Hosting max connections
SupabaseSSupabase / help-and-questions
3mo ago