Re: PG_SETMASK() archeology

2023-01-20 Thread Nathan Bossart
On Fri, Jan 13, 2023 at 02:00:05PM +1300, Thomas Munro wrote: > The reason we introduced PG_SETMASK() in the first place was to > support one particular system that was very slow to adopt the POSIX > signals stuff: NeXTSTEP 3.x. > > From some time in the dark age before our current repo begins

PG_SETMASK() archeology

2023-01-12 Thread Thomas Munro
Hi, This is a follow-up for commit c94ae9d8. It's in the spirit of other recent changes to remove noise from ancient pre-standard systems. The reason we introduced PG_SETMASK() in the first place was to support one particular system that was very slow to adopt the POSIX signals stuff: NeXTSTEP