Re: pgsql: Use SIGURG rather than SIGUSR1 for latches.

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Use SIGURG rather than SIGUSR1 for latches.
Date: 2021-04-18 23:36:44
Message-ID: CA+hUKGJ=-aOZ=wa7XLcwJN7FOrzgcewjSE3w_vY9uHx-Cmf9ZQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sun, Apr 18, 2021 at 1:28 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)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.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2021-04-19 01:15:56 pgsql: Replace magic constants for seek() calls in perl scripts
Previous Message Thomas Munro 2021-04-18 22:38:30 pgsql: Explain postmaster's treatment of SIGURG.