Re: convert libpgport's pqsignal() to a void function

On Thu, Jan 16, 2025 at 12:47 PM Nathan Bossart
<nathandbossart(at)gmail(dot)com> wrote:
> On Thu, Jan 16, 2025 at 11:07:41AM +1300, Thomas Munro wrote:
> > +1 for your idea of not defining them at all outside the backend, it's
> > just confusing noise.
>
> I tried that, but these extra signals are needed even in the frontend for
> pgkill(), etc.

Right, of course.

(In an unconf in Vancouver, a group of us were plotting that there
should be a more explicit control socket to talk to the postmaster, on
all OSes, to get current status, recovery progress, etc, and also
support shutdown commands more explicitly. If you separately turn all
the backend IPC signals into interrupts (CF 5118 and further work like
that), and these cluster-level ones you just mentioned into commands
in the hypothetical new cluster control protocol, then you don't need
fake signals for Windows anymore, but apparently I got ahead of myself
with that comment :-))

> My next thought was to simply ignore signal() errors for
> the extra signals, but I don't think that's very nice because it just masks
> broken code. Finally, I settled on modifying initdb's setup_signals() to
> use WIN32 checks instead of checking for the signals themselves. This is
> how it's done elsewhere, and this is apparently all that's needed to make
> cfbot's Windows run happy.

Cool.

> I've also attached a 0002 that removes the redefinitions of SIG_ERR and
> friends. That looks good on cfbot, but we'll see what the buildfarm has to
> say...

Ditto.