Re: Proposal for Signal Detection Refactoring - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Proposal for Signal Detection Refactoring
Date
Msg-id 20180921044611.GH1338@paquier.xyz
Whole thread Raw
In response to Proposal for Signal Detection Refactoring  (Chris Travers <chris.travers@adjust.com>)
Responses Re: Proposal for Signal Detection Refactoring  (Andres Freund <andres@anarazel.de>)
Re: Proposal for Signal Detection Refactoring  (Chris Travers <chris.travers@adjust.com>)
List pgsql-hackers
On Thu, Sep 20, 2018 at 03:08:34PM +0200, Chris Travers wrote:
> So here's a small patch.  I will add it for the next commit fest unless
> anyone has any reason I shouldn't.

-       return InterruptPending && (QueryCancelPending || ProcDiePending);
+       return PENDING_INTERRUPT_LEVEL() >= QUERY_CANCEL;

This is pretty similar to lock levels, where it is pretty hard to put a
strict monotone hierarchy when it comes to such interruptions.  The new
code does not seem like an improvment either, as for example in the code
mentioned above, you know directly what are the actions involved, which
is not the case with the new code style.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Strange failure in LWLock on skink in REL9_5_STABLE
Next
From: Andres Freund
Date:
Subject: Re: Proposal for Signal Detection Refactoring