Horton

Re: Timeout parameters

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: "Nagaura, Ryohei" <nagaura.ryohei@jp.fujitsu.com>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, "Jamison, Kirk" <k.jamison@jp.fujitsu.com>, "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>, Michael Paquier <michael@paquier.xyz>, "AYahorau@ibagroup.eu" <AYahorau@ibagroup.eu>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "MikalaiKeida@ibagroup.eu" <MikalaiKeida@ibagroup.eu>
Date: 2019-03-12T17:05:20Z
Lists: pgsql-hackers 
On Sun, Mar 10, 2019 at 10:25 PM Nagaura, Ryohei
<nagaura.ryohei@jp.fujitsu.com> wrote:
> The main purpose of this parameter is to avoid client's waiting for DB server infinitely, not reducing the server's burden.
> This results in not waiting end-user, which is most important.

+1.  If the server fails to detect that the client has gone away,
that's the server's problem.  The client is entirely entitled to be
selfish if it so wishes.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Add support TCP user timeout in libpq and the backend server