Re: stopgap fix for signal handling during restore_command - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: stopgap fix for signal handling during restore_command
Date
Msg-id CA+hUKGLJuRBN=ZmaWK1CsHsCUq_6sHkE4LjKJPt=EMS_NQszvg@mail.gmail.com
Whole thread Raw
In response to Re: stopgap fix for signal handling during restore_command  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Fri, Feb 24, 2023 at 1:25 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> ENOCOFFEE

Erm, I realised after sending that I'd accidentally sent a version
that uses fork() anyway, and now if I change it back to vfork() it
doesn't fail the way I wanted to demonstrate, at least on Linux.  I
don't have time or desire to dig into how Linux vfork() really works
so I'll leave it at that... but the patch as posted does seem to be a
useful tool for understanding this failure... please just ignore the
confused comments about fork() vs vfork() therein.



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: pgsql: Refactor to add pg_strcoll(), pg_strxfrm(), and variants.
Next
From: Justin Pryzby
Date:
Subject: Re: Add LZ4 compression in pg_dump