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: Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Use SIGURG rather than SIGUSR1 for latches.
Date: 2021-04-15 10:50:56
Message-ID: CA+hUKG++4qXP3oWfN5MT58TD-NMJuzmseRFE-yPc_CeJiJMVyg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Apr 15, 2021 at 2:26 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2021-04-15 14:16:09 pgsql: doc: Add missing COMPRESSION into CREATE TABLE synopsis.
Previous Message Michael Paquier 2021-04-15 07:46:24 pgsql: doc: Simplify example of HISTFILE for psql