| From: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
|---|---|
| To: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Max connection exceeded |
| Date: | 2023-08-31 20:08:10 |
| Message-ID: | CAJk5AtZEUwQZw1wUku1YeY2dkYG22GJDNN2C7+f2vqSa7yta4g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thank you!
On Fri, 1 Sep, 2023, 1:09 AM Scott Ribe, <scott_ribe(at)elevated-dev(dot)com>
wrote:
> > On Aug 31, 2023, at 1:05 PM, David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> >
> > On Thu, Aug 31, 2023 at 9:22 AM Rajesh Kumar <
> rajeshkumar(dot)dba09(at)gmail(dot)com> wrote:
> > How do I resolve max connection exceed issue apart from closing idle
> connections ?
> >
> > Raise the limit.
> > Use a connection pooler in the application.
> > Use a standalone connection pooler.
> >
> > David J.
>
> Also check for application bugs leaking connections.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vadim V | 2023-08-31 22:21:22 | LOG: invalid resource manager ID 130 at 1398/A871F88 |
| Previous Message | Scott Ribe | 2023-08-31 19:38:56 | Re: Max connection exceeded |