aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-03-15 13:26:26 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2017-03-15 13:26:26 -0400
commitb5dd50f2c0ad8edcc3145aabe18788d448bf940d (patch)
tree5e9ebca26be2da48d6645f3ea66cd551ec0a5436 /contrib/postgres_fdw/postgres_fdw.c
parent1ea60ad602f9e97246958b721c8fa7c713aa86eb (diff)
downloadpostgresql-b5dd50f2c0ad8edcc3145aabe18788d448bf940d.tar.gz
postgresql-b5dd50f2c0ad8edcc3145aabe18788d448bf940d.zip
Rewrite async-connection loop in libpqwalreceiver.c, once again.
The original coding in commit 1e8a85009 didn't use PQconnectPoll per spec, and while the rewrite in e434ad39a is closer, it still doesn't guarantee to wait until the socket is read-ready or write-ready (as appropriate) before calling PQconnectPoll. It's not clear whether that omission is causing the continuing failures on buildfarm member bowerbird; but given the lack of other explanations meeting the available facts, let's tighten that up and see what happens. An independent issue in the same loop was that it had a race condition whereby it could clear the process's latch without having serviced an interrupt request, causing failure to respond to a cancel while waiting for connection (the very problem 1e8a85009 was meant to fix). Discussion: https://postgr.es/m/7295.1489596949@sss.pgh.pa.us
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions