From: | Goran Pulevic <goranmp(at)gmail(dot)com> |
---|---|
To: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Idle_session_timeout |
Date: | 2023-10-04 16:23:22 |
Message-ID: | CABvV9a1cUJO=NnE_-jP+sTJ9xqB+Crfa65-yErJTS5F0j5pWnQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
You need to talk to your application team and find out about their
connection related timeouts. Things like max-idle-time, server-lifetime,
etc. (They almost certainly use a db library which implements some kind of
client side connection pool).
In short: their timeouts should be lower than the server's
idle_session_timeout.
Something like: max-idle-time < server-lifetime < idle_session_timeout
On Wed, 4 Oct 2023 at 17:41, Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com>
wrote:
> Hi all,
>
> I was facing issue with idle connections not closed.
>
> So, I thought of automating it and set the parameter idle_session_timeout
> to 5min. But I got a message from application team that they are getting
> jdbc error continuously and they are saying connection is getting
> terminated. So I had to turn it off now.
>
>
> How to use this parameter correctly?
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | SOzcn | 2023-10-04 18:13:40 | Timeout Issue |
Previous Message | Scott Ribe | 2023-10-04 15:51:19 | Re: Idle_session_timeout |