public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Robert Haas <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: SIGQUIT handling, redux
Date: Thu, 10 Sep 2020 16:29:23 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+Tgmobn6yDe69m_R8n-nrFjxsFAjwdOr5eiPVdd_Qx7+g8P=g@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<CA+TgmoZc6QQoFeWJUj0c5e7bqhMaq=LnwTSFtUin-euz-u1HZw@mail.gmail.com>
	<[email protected]>
	<CA+Tgmobn6yDe69m_R8n-nrFjxsFAjwdOr5eiPVdd_Qx7+g8P=g@mail.gmail.com>

Robert Haas <[email protected]> writes:
> On Thu, Sep 10, 2020 at 12:56 PM Tom Lane <[email protected]> wrote:
>> Also, man that CHECK_FOR_INTERRUPTS() looks like trouble.
>> Could we take that out?

> Maybe I'm missing something, but why wouldn't that be a horrible idea?
> We do not want to have long waits where we refuse to respond to
> interrupts.

It might be appropriate for some of the callers to do it.  But I don't
see any great argument why ProcWaitForSignal itself has to do it.

			regards, tom lane

view thread (21+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: SIGQUIT handling, redux
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox