| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Johnathan Tiamoh <johnathantiamoh(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pooler error : client _idle_timeout |
| Date: | 2024-02-20 05:08:44 |
| Message-ID: | CAKFQuwawecJ2n8MF1E0Ndq4ZLF4erqCDS7gCyDYC-rRqFSokjw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday, February 19, 2024, Johnathan Tiamoh <johnathantiamoh(at)gmail(dot)com>
wrote:
>
> Please, I need help to fix this issue. I have increase client
> _idle_timeout from 15 minutes to 30 minutes and still facing the
> same problem.
>
>
Don’t connect through a pooler.
For a more helpful reply you need to actually show your work. What pooler
you are using, how you are connecting.
Poolers don’t tend to play nice with clients that want to supply connection
settings upfront. Either tell the client to not do that or don’t use a
pooler - the server itself is quite content with connection settings.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-02-20 08:42:51 | Re: Identifying optimizer usage of indexed expressions |
| Previous Message | Johnathan Tiamoh | 2024-02-20 04:58:14 | pooler error : client _idle_timeout |