From: | "Nagaura, Ryohei" <nagaura(dot)ryohei(at)jp(dot)fujitsu(dot)com> |
---|---|
To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "Jamison, Kirk" <k(dot)jamison(at)jp(dot)fujitsu(dot)com> |
Cc: | 'Michael Paquier' <michael(at)paquier(dot)xyz>, "AYahorau(at)ibagroup(dot)eu" <AYahorau(at)ibagroup(dot)eu>, 'Fabien COELHO' <coelho(at)cri(dot)ensmp(dot)fr>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>, "MikalaiKeida(at)ibagroup(dot)eu" <MikalaiKeida(at)ibagroup(dot)eu> |
Subject: | RE: Timeout parameters |
Date: | 2019-02-25 04:48:36 |
Message-ID: | EDA4195584F5064680D8130B1CA91C453E96D6@G01JPEXMBYT04 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi, all.
Thank you for discussion.
I made documentation about socket_timeout and reflected Tsunakawa-san's comment in the new patch.
# Mainly only fixing documentation...
The current documentation of socket_timeout is as follows:
socket_timeout
Controls the number of second of client's waiting time for individual socket read/write operations. This can be used both as a force
global query timeout and network problems detector. A value of zero (the default) turns this off.
Best regards,
---------------------
Ryohei Nagaura
Attachment | Content-Type | Size |
---|---|---|
TCP_backend_v5.patch | application/octet-stream | 6.0 KB |
TCP_interface_v5.patch | application/octet-stream | 4.8 KB |
socket_timeout_v5.patch | application/octet-stream | 3.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2019-02-25 04:52:14 | Re: shared-memory based stats collector |
Previous Message | Tsunakawa, Takayuki | 2019-02-25 02:38:05 | RE: reloption to prevent VACUUM from truncating empty pages at the end of relation |