[pgpool-hackers: 2696] Re: [pgpool-committers: 4513] pgpool: Set TCP_NODELAY and non blocking to frontend socket.

Tatsuo Ishii ishii at sraoss.co.jp
Tue Jan 30 10:39:42 JST 2018


It seems we forgot to set TCP_NODELAY option to frontend socket since
day 0. PostgreSQL always sets the flag, and we set the flag for
backend sockets, so I decided to set the flag to the frontend socket
because it's more consistent.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


From: Tatsuo Ishii <ishii at postgresql.org>
Subject: [pgpool-committers: 4513] pgpool: Set TCP_NODELAY and non blocking to frontend socket.
Date: Mon, 29 Jan 2018 05:00:15 +0000
Message-ID: <E1eg1YF-00083B-DP at gothos.postgresql.org>

> Set TCP_NODELAY and non blocking to frontend socket.
> 
> TCP_NODELAY is employed by PostgreSQL, so do we it.
> 
> Listen fd is set to non blocking. To make sure accept fd is set to non
> blocking.
> 
> Branch
> ------
> master
> 
> Details
> -------
> https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=3fe84f82537732ae2240e6e87d970d9193e01c93
> 
> Modified Files
> --------------
> src/protocol/child.c | 27 ++++++++++++++++++++++++++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
> 


More information about the pgpool-hackers mailing list