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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: "tsunakawa(dot)takay(at)fujitsu(dot)com" <tsunakawa(dot)takay(at)fujitsu(dot)com>
Cc: Maksim Milyutin <milyutinma(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Zhihong Yu <zyu(at)yugabyte(dot)com>
Subject: Re: Add client connection check during the execution of the query
Date: 2021-04-30 02:23:10
Message-ID: CA+hUKG+tg5fWWvF5WbwEt4VO69Tj9o6F9mq-wd9kHHxDhUiBzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Apr 3, 2021 at 9:27 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Pushed! Thanks to all who contributed.

Here's something I wanted to park here to look into for the next
cycle: it turns out that kqueue's EV_EOF flag also has the right
semantics for this. That leads to the idea of exposing the event via
the WaitEventSet API, and would the bring
client_connection_check_interval feature to 6/10 of our OSes, up from
2/10. Maybe Windows' FD_CLOSE event could get us up to 7/10, not
sure.

Attachment Content-Type Size
0001-Add-WL_SOCKET_CLOSED-for-socket-shutdown-events.patch text/x-patch 6.9 KB
0002-Use-WL_SOCKET_CLOSED-for-client_connection_check_int.patch text/x-patch 4.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2021-04-30 02:46:15 Re: Enhanced error message to include hint messages for redundant options error
Previous Message Justin Pryzby 2021-04-30 01:37:46 Re: Remove redundant variable from transformCreateStmt