From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Ricardo Ungureanu <ricardoungureanu@gmail.com>, kimon.krenz@part9.com,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16827: macOS interrupted syscall leads to a crash
In-reply-to: <20210122173535.5zzud4b6ffk4mym6@alap3.anarazel.de>
References: <16827-7606aeb21d38c228@postgresql.org>
 <20210115210548.zfbnulfeanmffmet@alap3.anarazel.de>
 <CAFHbkwjPXHgWb15wsmaCMuYOOF2Fm6sBVj9Sv1LbwRav75KsRg@mail.gmail.com>
 <20210122173535.5zzud4b6ffk4mym6@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Fri, 22 Jan 2021 09:35:35 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1168200.1611337651.1@sss.pgh.pa.us>
Date: Fri, 22 Jan 2021 12:47:31 -0500
Message-ID: <1168201.1611337651@sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> Tom, all, this seems like a serious problem likely to become more
> widespread. I don't really know how we can reasonably address this
> short-term, adding EINTR handling to all the places that don't yet have
> it (and ensuring that it stays that way) seems like it's a lot to backport.

The only idea that comes to mind is to invent a wrapper for open
(and other affected syscalls) that adds a loop-on-EINTR.  Ugly,
and it would not fix third-party extensions until they're recompiled.

My inclination is to regard this as something that's Apple's problem,
at least for now.  Perhaps they'll realize what a disaster it is.
(OTOH, they've proven pretty mulish on making SIP usable...)

			regards, tom lane