| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Ram Pratap Maurya <ram(dot)maurya(at)lavainternational(dot)in> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Posgresql-13 Bug (idle_in_transaction_session_timeout) |
| Date: | 2022-05-11 08:35:34 |
| Message-ID: | CAD21AoC4sb5sQEGmLtMzR0zSzUHWNLVQECpU5pF2ck8t5f+sbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On Wed, May 11, 2022 at 4:52 PM Ram Pratap Maurya
<ram(dot)maurya(at)lavainternational(dot)in> wrote:
>
> Hi Team,
>
>
>
> I have enable parameter “idle_in_transaction_session_timeout” in Postgresql-13 conf file.
>
> But still Ideal connection exist in system more the defined ideal time.
>
>
>
> I have defined ideal time 28800000 milliseconds. second (8Hrs) .
>
>
>
> Can you please check and suggest , screen shot attached for reference.
idle_in_transaction_session_timeout is a timeout for sessions that
have been idle within an open transaction. But looking at the
screenshot you shared, the processes are in an idle state, not an
idle-in-transaction state. idle_session_timeout sets a timeout for
sessions that are in an idle state but it's available in PostgreSQL 14
or later.
Regards,
--
Masahiko Sawada
EDB: https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ram Pratap Maurya | 2022-05-11 09:19:05 | RE: Posgresql-13 Bug (idle_in_transaction_session_timeout) |
| Previous Message | Ram Pratap Maurya | 2022-05-11 07:52:24 | Posgresql-13 Bug (idle_in_transaction_session_timeout) |