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

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: thomas(dot)munro(at)gmail(dot)com
Cc: s(dot)cherkashin(at)postgrespro(dot)ru, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Add client connection check during the execution of the query
Date: 2019-07-05 06:42:04
Message-ID: 20190705.154204.2022066057531003556.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> This seems like a reasonable idea to me. There is no point in running
> a monster 24 hour OLAP query if your client has gone away. It's using
> MSG_PEEK which is POSIX, and I can't immediately think of any reason
> why it's not safe to try to peek at a byte in that socket at any time.

I am not familiar with Windows but I accidentally found this article
written by Microsoft:

https://support.microsoft.com/en-us/help/192599/info-avoid-data-peeking-in-winsock

It seems using MSG_PEEK is not recommended by Microsoft.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-07-05 06:47:32 Re: improve PQexec documentation
Previous Message Andrey Lepikhov 2019-07-05 06:32:39 Re: [HACKERS] Partition-wise aggregation/grouping