Re: BUG #18075: configuration variable idle_session_timeout not working as expected

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #18075: configuration variable idle_session_timeout not working as expected
Дата
Msg-id CAKFQuwakcX7pD4dnRErs0Vr5CcgFt9XES8K3VrUF9nXON9Ug2A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #18075: configuration variable idle_session_timeout not working as expected  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #18075: configuration variable idle_session_timeout not working as expected  (Muhammad Ali Ansari <maliansari.coder@gmail.com>)
Список pgsql-bugs
On Tue, Aug 29, 2023 at 2:46 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Tuesday, August 29, 2023, PG Bug reporting form <noreply@postgresql.org>
> wrote:
>> I have set the idle_session_timeout variable as 60000 making it 60 seconds
>> 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.

Also, the OP didn't say *how* he set idle_session_timeout.  That
pg_settings extract only proves that 60000 is the prevailing value in
the session where that was done.  It's possible that the value was
only set locally, or in some other way that didn't affect those other
sessions at all.


Yeah, the fact all of those are for "apiuser" suggests to me that user has their own setting for this which takes precedence over the server default.

The output of \drds would be more informative than just looking at some unknown session's value.

David J.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #18076: Consistently receiving Signal 7 and Signal 11 errors
Следующее
От: Muhammad Ali Ansari
Дата:
Сообщение: Re: BUG #18075: configuration variable idle_session_timeout not working as expected