From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Andres Freund <andres@anarazel.de>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: EINTR in ftruncate()
Date: Thu, 14 Jul 2022 17:34:42 -0400
Message-ID: <3153247.1657834482@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+hUKGK2pLvUOM-EoRLQxL-fC5hFzi6Xa9za9hNmAf2DteVDFg@mail.gmail.com>
References: <20220714144652.jph7exiywushg4gc@alvherre.pgsql>
<2835511.1657812444@sss.pgh.pa.us>
<CA+hUKGK2pLvUOM-EoRLQxL-fC5hFzi6Xa9za9hNmAf2DteVDFg@mail.gmail.com>
Thomas Munro <thomas.munro@gmail.com> writes:
> So why would I add another wrapper like PG_SETMASK and leave it
> unimplemented for now on Windows, when I could just use sigprocmask()
> directly and leave it unimplemented for now on Windows?
Fair enough, I guess. No objection to this patch.
(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.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, thomas.munro@gmail.com, alvherre@alvh.no-ip.org, andres@anarazel.de, pgsql-hackers@lists.postgresql.org
Subject: Re: EINTR in ftruncate()
In-Reply-To: <3153247.1657834482@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox