diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-04-24 18:29:03 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-04-24 18:29:03 -0400 |
| commit | 64925603c972aa3a9f1d4c42686dba67f1a7e9d0 (patch) | |
| tree | 6bb1f30ee0e0d05946394f59cc8810cd99f41400 /contrib/postgres_fdw/postgres_fdw.c | |
| parent | 81069a9efc5a374dd39874a161f456f0fb3afba4 (diff) | |
| download | postgresql-64925603c972aa3a9f1d4c42686dba67f1a7e9d0.tar.gz postgresql-64925603c972aa3a9f1d4c42686dba67f1a7e9d0.zip | |
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
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions