public inbox for [email protected]help / color / mirror / Atom feed
Re: Getting error "too many clients already" despite having a db connection limit set 3+ messages / 2 participants [nested] [flat]
* Re: Getting error "too many clients already" despite having a db connection limit set @ 2025-06-16 17:21 Adrian Klaver <[email protected]> 2025-06-16 18:09 ` Re: Getting error "too many clients already" despite having a db connection limit set David G. Johnston <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: Adrian Klaver @ 2025-06-16 17:21 UTC (permalink / raw) To: adolfo flores <[email protected]>; [email protected] On 6/16/25 09:29, adolfo flores wrote: > Hello Team, > > I hope you can help me with an issue we're experiencing. We have an app > running on Kubernetes that opens a huge number of connections within a > couple of seconds. > > The database that the app connects to, is configured with a connection > limit of 30% of the max_connections setting. Despite this limit being I am not understanding the above. The connection limit from the database side is going to be the value for max_connections. It is not clear to me what "... connection limit of 30% of the max_connections setting" is referring to? I suggest providing the actual numbers you are working with as well as the locations where the numbers are being set. > set for that database, we're seeing the following errors in the > PostgreSQL logs: > > FATAL: sorry, too many clients already > FATAL: remaining connection slots are reserved for roles with the > SUPERUSER attribute > > > Is it expected behavior to reach the max_connections limit when that app > opens many connections in a short period of time, even if a connection > limit is set for that database and everything else uses no more than 10% > of the max_connections? > > Or any idea on what could be happening? > > > Regards. > > Adolfo F. -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Getting error "too many clients already" despite having a db connection limit set 2025-06-16 17:21 Re: Getting error "too many clients already" despite having a db connection limit set Adrian Klaver <[email protected]> @ 2025-06-16 18:09 ` David G. Johnston <[email protected]> 2025-06-16 18:13 ` Re: Getting error "too many clients already" despite having a db connection limit set Adrian Klaver <[email protected]> 0 siblings, 1 reply; 3+ messages in thread From: David G. Johnston @ 2025-06-16 18:09 UTC (permalink / raw) To: Adrian Klaver <[email protected]>; +Cc: adolfo flores <[email protected]>; [email protected] On Mon, Jun 16, 2025, 10:21 Adrian Klaver <[email protected]> wrote: > On 6/16/25 09:29, adolfo flores wrote: > > Hello Team, > > > > I hope you can help me with an issue we're experiencing. We have an app > > running on Kubernetes that opens a huge number of connections within a > > couple of seconds. > > > > The database that the app connects to, is configured with a connection > > limit of 30% of the max_connections setting. Despite this limit being > > I am not understanding the above. The connection limit from the database > side is going to be the value for max_connections. It is not clear to me > what "... connection limit of 30% of the max_connections setting" is > referring to? > See "alter database ... set" David J. ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Getting error "too many clients already" despite having a db connection limit set 2025-06-16 17:21 Re: Getting error "too many clients already" despite having a db connection limit set Adrian Klaver <[email protected]> 2025-06-16 18:09 ` Re: Getting error "too many clients already" despite having a db connection limit set David G. Johnston <[email protected]> @ 2025-06-16 18:13 ` Adrian Klaver <[email protected]> 0 siblings, 0 replies; 3+ messages in thread From: Adrian Klaver @ 2025-06-16 18:13 UTC (permalink / raw) To: David G. Johnston <[email protected]>; +Cc: adolfo flores <[email protected]>; [email protected] On 6/16/25 11:09 AM, David G. Johnston wrote: > > > > I am not understanding the above. The connection limit from the > database > side is going to be the value for max_connections. It is not clear > to me > what "... connection limit of 30% of the max_connections setting" is > referring to? > > > See "alter database ... set" Aah, forgot about that. > > David J. > > -- Adrian Klaver [email protected] ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2025-06-16 18:13 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-06-16 17:21 Re: Getting error "too many clients already" despite having a db connection limit set Adrian Klaver <[email protected]> 2025-06-16 18:09 ` David G. Johnston <[email protected]> 2025-06-16 18:13 ` Adrian Klaver <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox