Re: EINTR in ftruncate() - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: EINTR in ftruncate()
Date
Msg-id CA+hUKGK5ax1AoFMvXksLROrxwB1=-EsT=7+6oUtCn47GbC9zjA@mail.gmail.com
Whole thread Raw
In response to Re: EINTR in ftruncate()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: EINTR in ftruncate()
List pgsql-hackers
On Sat, Jul 16, 2022 at 1:28 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
> > On Fri, Jul 15, 2022 at 9:34 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> (Someday we oughta go ahead and make our Windows signal API look more
> >> like POSIX, as I suggested back in 2015.  I'm still not taking
> >> point on that, though.)
>
> > For the sigprocmask() part, here's a patch that passes CI.  Only the
> > SIG_SETMASK case is actually exercised by our current code, though.
>
> Passes an eyeball check, but I can't actually test it.

Thanks.  Pushed.

I'm not brave enough to try to write a replacement sigaction() yet,
but it does appear that we could rip more ugliness and inconsistencies
that way, eg sa_mask.



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Handle infinite recursion in logical replication setup
Next
From: John Naylor
Date:
Subject: Re: Improving scalability of Parallel Bitmap Heap/Index Scan