From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | "maliansari(dot)coder(at)gmail(dot)com" <maliansari(dot)coder(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #18075: configuration variable idle_session_timeout not working as expected |
Date: | 2023-08-29 21:12:00 |
Message-ID: | CAKFQuwbgj3i3321PfKeZt597BDH9NisOAJ3YJF19btcatQ1kBQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tuesday, August 29, 2023, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18075
> Logged by: Muhammad Ali Ansari
> Email address: maliansari(dot)coder(at)gmail(dot)com
> PostgreSQL version: 15.4
> Operating system: ubuntu 22.04
> Description:
>
> I have set the idle_session_timeout variable as 60000 making it 60 seconds
>
> EXTRACT(MINUTE FROM (current_timestamp - state_change)) as duration
>
> datname | pid | query | usename | client_addr | client_port | state |
> backend_xid | duration
> ----------+-----+--------+---------+-------------+----------
> ---+-------+-------------+----------
> postgres | 975 | COMMIT | apiuser | ::1 | 45748 | idle |
>
> | 28
>
>
> As we can see, it shows that the time is way more than 1 minute now it is
> 28
> minutes and they are still idle and still open in postgres and not
> disconnected as expected.
>
Not sure how you got 28 minutes from 45748…which is large enough that it is
probable those sessions started before you changed the timeout and so are
not affected by it.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Sanford | 2023-08-29 21:37:13 | Re: BUG #18076: Consistently receiving Signal 7 and Signal 11 errors |
Previous Message | PG Bug reporting form | 2023-08-29 20:26:18 | BUG #18076: Consistently receiving Signal 7 and Signal 11 errors |