Revert "Use pselect(2) not select(2), if available, to wait in postmaster's loop."
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 24 Apr 2017 22:29:03 +0000 (18:29 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 24 Apr 2017 22:29:03 +0000 (18:29 -0400)
commit64925603c972aa3a9f1d4c42686dba67f1a7e9d0
tree6bb1f30ee0e0d05946394f59cc8810cd99f41400
parent81069a9efc5a374dd39874a161f456f0fb3afba4
Revert "Use pselect(2) not select(2), if available, to wait in postmaster's loop."

This reverts commit 81069a9efc5a374dd39874a161f456f0fb3afba4.

Buildfarm results suggest that some platforms have versions of pselect(2)
that are not merely non-atomic, but flat out non-functional.  Revert the
use-pselect patch to confirm this diagnosis (and exclude the no-SA_RESTART
patch as the source of trouble).  If it's so, we should probably look into
blacklisting specific platforms that have broken pselect.

Discussion: https://postgr.es/m/9696.1493072081@sss.pgh.pa.us
configure
configure.in
src/backend/postmaster/postmaster.c
src/include/pg_config.h.in
src/include/pg_config.h.win32