Horton

Re: Add client connection check during the execution of the query

Tatsuo Ishii <ishii@sraoss.co.jp>

View thread View on postgr.es
From: Tatsuo Ishii <ishii@sraoss.co.jp>
To: thomas.munro@gmail.com
Cc: ishii@sraoss.co.jp, s.kelvich@postgrespro.ru, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Date: 2019-07-18T04:43:08Z
Lists: pgsql-hackers 
> Yeah, the timer logic is wrong.  I didn't have time to look into it
> but with truss/strace for some reason I see 3 setitimer() syscalls for
> every query, but I think this doesn't even need to set the timer for
> every query.

Hum. I see 2 settimer(), instead of 3.

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

Commits

  1. Add WL_SOCKET_CLOSED for socket shutdown events.

  2. Use WL_SOCKET_CLOSED for client_connection_check_interval.

  3. Detect POLLHUP/POLLRDHUP while running queries.

  4. Improve timeout.c's handling of repeated timeout set/cancel.