RE: Timeout parameters

Nagaura, Ryohei <nagaura.ryohei@jp.fujitsu.com>

From: "Nagaura, Ryohei" <nagaura.ryohei@jp.fujitsu.com>

To: "Nagaura, Ryohei" <nagaura.ryohei@jp.fujitsu.com>, "Jamison, Kirk" <k.jamison@jp.fujitsu.com>

Cc: "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>, 'Michael Paquier' <michael@paquier.xyz>, "AYahorau@ibagroup.eu" <AYahorau@ibagroup.eu>, "'Fabien COELHO'" <coelho@cri.ensmp.fr>, "'pgsql-hackers@postgresql.org'" <pgsql-hackers@postgresql.org>, "MikalaiKeida@ibagroup.eu" <MikalaiKeida@ibagroup.eu>

Date: 2019-02-28T03:07:05Z

Lists: pgsql-hackers

Attachments

TCP_backend_v8.patch (application/octet-stream) patch v8
TCP_interface_v8.patch (application/octet-stream) patch v8
socket_timeout_v7.patch (application/octet-stream) patch v7

Hi,

I rewrote two TCP_USER_TIMEOUT patches.
I changed the third argument of setsockopt() from 18 to TCP_USER_TIMEOUT.

This revision has the following two merits.
* Improve readability of source
* Even if the definition of TCP_USER_TIMEOUT is changed, it is not affected.
  e.g., in the current linux, TCP_USER_TIMEOUT is defined, but even if it is changed to 19, it 'll be available.

Best regards,
---------------------
Ryohei Nagaura

Commits

Add support TCP user timeout in libpq and the backend server
- 249d64999615 12.0 landed