Re: Interrupts vs signals - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Interrupts vs signals
Date
Msg-id CA+TgmoZESA_RrkPa7odtGAiKFDrmYp0rqZ0vVb_w-U4NFtYwqQ@mail.gmail.com
Whole thread Raw
In response to Re: Interrupts vs signals  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Mon, Nov 18, 2024 at 11:09 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> Names don't match here.  I prefer _CONTINUE.  As for the general one,
> I'm on the fence about INTERRUPT_GENERAL_WAKEUP, since wakeups aren't
> necessarily involved, but I don't have a specific better idea so I'm
> not objecting...  Perhaps it's more like INTERRUPT_GENERAL_NOTIFY,
> except that _NOTIFY is already a well known thing, and the procsignal
> patch introduces INTERRUPT_NOTIFY...

INTERRUPT_GENERAL with no third word isn't out of the question, either.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Michel Pelletier
Date:
Subject: Re: Using Expanded Objects other than Arrays from plpgsql
Next
From: Jeff Davis
Date:
Subject: Re: Update Unicode data to Unicode 16.0.0