pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: maliansari.coder@gmail.com <maliansari.coder@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #18075: configuration variable idle_session_timeout not working as expected
Date: Tue, 29 Aug 2023 17:46:49 -0400
Message-ID: <49264.1693345609@sss.pgh.pa.us> (raw)
In-Reply-To: <CAKFQuwbgj3i3321PfKeZt597BDH9NisOAJ3YJF19btcatQ1kBQ@mail.gmail.com>
References: <18075-d8a1bf11f070743e@postgresql.org>
	<CAKFQuwbgj3i3321PfKeZt597BDH9NisOAJ3YJF19btcatQ1kBQ@mail.gmail.com>

"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.

> 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.

I believe idle_session_timeout is consulted when the session goes
idle, and we either set a timeout interrupt or not.  The prevailing
value might change after that, but it won't affect existing sessions
until they next go idle.  I do not regard that as a bug.

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.

			regards, tom lane





view thread (13+ messages)  latest in thread

Message-ID: <49264.1693345609@sss.pgh.pa.us>
Permalink:  ../49264.1693345609@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/49264.1693345609@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, david.g.johnston@gmail.com, maliansari.coder@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18075: configuration variable idle_session_timeout not working as expected
  In-Reply-To: <49264.1693345609@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox