Re: We shouldn't signal process groups with SIGQUIT

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Subject: Re: We shouldn't signal process groups with SIGQUIT
Date: 2023-03-02 01:20:58
Message-ID: CA+hUKG+wdis8FuTp9F2GoyLgZGUtQoBy-=OskH3kp91rEx6ebg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 2, 2023 at 1:09 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2023-03-02 12:29:28 +1300, Thomas Munro wrote:
> > ... Huh... what am I missing? I
> > thought the only risk was handlers running in the opposite of send
> > order because they 'overlapped', not non-handler code being allowed to
> > run in between.
>
> I see ProcessInterrupts() being called too - but it's independent of the
> changes we discuss here. The reason for it is the CFI() at the end of
> errfinish().

Ahh, right, I see.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-03-02 01:22:21 Re: [HACKERS] make async slave to wait for lsn to be replayed
Previous Message Tom Lane 2023-03-02 01:15:34 Re: typedef struct LogicalDecodingContext