Re: [PATCH] ProcessInterrupts_hook - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] ProcessInterrupts_hook
Date
Msg-id 4156999.1616183168@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] ProcessInterrupts_hook  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] ProcessInterrupts_hook  (Craig Ringer <craig.ringer@enterprisedb.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Mar 19, 2021 at 3:25 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I'm not very comfortable about the idea of having the postmaster set
>> child processes' latches ... that doesn't sound terribly safe from the
>> standpoint of not allowing the postmaster to mess with shared memory
>> state that could cause it to block or crash.  If we already do that
>> elsewhere, then OK, but I don't think we do.

> It should be unnecessary anyway. We changed it a while back to make
> any SIGUSR1 set the latch ....

Hmm, so the postmaster could send SIGUSR1 without setting any particular
pmsignal reason?  Yeah, I suppose that could work.  Or we could recast
this as being a new pmsignal reason.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Custom compression methods
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Identify LWLocks in tracepoints