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+hUKG++4qXP3oWfN5MT58TD-NMJuzmseRFE-yPc_CeJiJMVyg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Use SIGURG rather than SIGUSR1 for latches.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Use SIGURG rather than SIGUSR1 for latches.  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-committers
On Thu, Apr 15, 2021 at 2:26 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> It's possible that that argument doesn't apply to the way SIGURG is used
> in this patch, but I don't see a good reason to ignore the convention of
> setting up the handler this way.

Yeah, will fix.  I don't think there is a bug here given the way
latches use shared memory flags, but it might as well be consistent.



pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: doc: Simplify example of HISTFILE for psql
Next
From: Fujii Masao
Date:
Subject: pgsql: doc: Add missing COMPRESSION into CREATE TABLE synopsis.