| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | adolfo flores <adolfoflores2211(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Getting error "too many clients already" despite having a db connection limit set |
| Date: | 2025-06-16 18:09:59 |
| Message-ID: | CAKFQuwa0t-L_zxuseJtOyf6F32V7pFdEw90wgyo769he+CdW4Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jun 16, 2025, 10:21 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-06-16 18:13:25 | Re: Getting error "too many clients already" despite having a db connection limit set |
| Previous Message | Adrian Klaver | 2025-06-16 17:21:39 | Re: Getting error "too many clients already" despite having a db connection limit set |