Re: pgsql: Use SIGURG rather than SIGUSR1 for latches. - Mailing list pgsql-committers

From Thomas Munro
Subject Re: pgsql: Use SIGURG rather than SIGUSR1 for latches.
Date
Msg-id CA+hUKGJ=-aOZ=wa7XLcwJN7FOrzgcewjSE3w_vY9uHx-Cmf9ZQ@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Use SIGURG rather than SIGUSR1 for latches.  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-committers
On Sun, Apr 18, 2021 at 1:28 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> Linux: "Blocked signals are never ignored, since the signal handler
> may change by the time it is unblocked."

I should add, that's what the source says.  The man page for
sigpending(2) makes the opposite claim in its NOTES section on my
Debian system (it helpfully describes the BSD behaviour instead), but
the man page is demonstrably wrong.



pgsql-committers by date:

Previous
From: Thomas Munro
Date:
Subject: pgsql: Explain postmaster's treatment of SIGURG.
Next
From: Michael Paquier
Date:
Subject: pgsql: Replace magic constants for seek() calls in perl scripts