| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Walters Che Ndoh <chendohw(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: killing idle_connections |
| Date: | 2020-12-01 02:59:50 |
| Message-ID: | CAKFQuwbJUW_N29kqP3Skjor6fTDtXEOVY3xnv7gKPxcFUVUHVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Monday, November 30, 2020, Walters Che Ndoh <chendohw(at)gmail(dot)com> wrote:
>
> Or should I not run the script in the first place since connection pooling
> handles idle connections?
>
That. Combined with the developers correctly handling connection
management in their code. The pooler doesn’t doesn’t fix bad code. It
lets you properly disconnect and reconnect constantly in the application
while minimizing the pain of doing so. Settings on the poolers came
surface the pain of bad usage more quickly, and should turn connection
failures into connection delays (which should eventually timeout).
Speaking off-the-cuff here...
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dischner, Anton | 2020-12-01 08:03:25 | AW: killing idle_connections |
| Previous Message | Walters Che Ndoh | 2020-12-01 02:49:39 | killing idle_connections |