From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Removing select(2) based latch (was Unportable implementation of background worker start) |
Date: | 2017-04-20 21:27:42 |
Message-ID: | 20505.1492723662@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2017-04-19 20:06:05 -0400, Tom Lane wrote:
>> We should check the buildfarm to see if the select() implementation is
>> being tested at all.
> I verified it's currently not (unless I made a mistake):
I did my own checking, and concur that only the MinGW buildfarm members
are reporting lacking poll(2) or poll.h. Since they also report lacking
sys/select.h, they must be falling through to the WAIT_USE_WIN32
implementation. So the WAIT_USE_SELECT implementation is going untested
in the buildfarm, and has been since before the WaitEventSet API existed
(I checked buildfarm records back to the start of 2016).
Aside from that empirical observation, we can make a standards-compliance
argument, which is that both poll(2) and poll.h are required by the Single
Unix Spec v2 (a/k/a POSIX 1997), which is what we've been taking as our
baseline requirement for Unix platforms for ten or fifteen years now.
In short: yeah, let's nuke the WAIT_USE_SELECT implementation.
It's dead code and it's unlikely to get resurrected.
BTW, noting that SUSv2 specifies <poll.h> not <sys/poll.h>, I wonder
whether we couldn't drop configure's test for the latter along with
the
#ifdef HAVE_SYS_POLL_H
#include <sys/poll.h>
#endif
stanzas we have in a couple of places. But that's a separate issue.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-04-20 21:30:24 | Re: DROP SUBSCRIPTION, query cancellations and slot handling |
Previous Message | Peter Eisentraut | 2017-04-20 21:25:07 | Re: DROP SUBSCRIPTION, query cancellations and slot handling |