From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | tony(dot)capobianco(at)bcbsma(dot)com |
Subject: | idle_session_timeout doc |
Date: | 2022-01-19 20:13:47 |
Message-ID: | 164262322735.31954.5814862771892121460@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/runtime-config-client.html
Description:
Is there a way to alter users idle_session_timeout setting? My
understanding is that it's a global setting. The last sentence indicates
you can apply an idle session timeout to particular users:
idle_session_timeout (integer)
Terminate any session that has been idle (that is, waiting for a client
query), but not within an open transaction, for longer than the specified
amount of time. If this value is specified without units, it is taken as
milliseconds. A value of zero (the default) disables the timeout.
Unlike the case with an open transaction, an idle session without a
transaction imposes no large costs on the server, so there is less need to
enable this timeout than idle_in_transaction_session_timeout.
Be wary of enforcing this timeout on connections made through
connection-pooling software or other middleware, as such a layer may not
react well to unexpected connection closure. It may be helpful to enable
this timeout only for interactive sessions, perhaps by applying it only to
particular users.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-01-19 21:26:20 | Re: idle_session_timeout doc |
Previous Message | Daniel Gustafsson | 2022-01-19 09:24:57 | Re: gettext instructions for Windows seems wrong |