aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_node.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2002-04-15 23:34:17 +0000
committerBruce Momjian <bruce@momjian.us>2002-04-15 23:34:17 +0000
commit394eec1068f1caea4c6ac4a3f2191eaef2a6719e (patch)
treeb4f795fbd896540369739947c8df3c24d81b21a3 /src/backend/parser/parse_node.c
parentb66cbc1fa26aebfcfecbfff7c92d804d083af843 (diff)
downloadpostgresql-394eec1068f1caea4c6ac4a3f2191eaef2a6719e.tar.gz
postgresql-394eec1068f1caea4c6ac4a3f2191eaef2a6719e.zip
Fix for EINTR returns from Win9X socket operations:
In summary, if a software writer implements timer events or other events which generate a signal with a timing fast enough to occur while libpq is inside connect(), then connect returns -EINTR. The code following the connect call does not handle this and generates an error message. The sum result is that the pg_connect() fails. If the timer or other event is right on the window of the connect() completion time, the pg_connect() may appear to work sporadically. If the event is too slow, pg_connect() will appear to always work and if the event is too fast, pg_connect() will always fail. David Ford
Diffstat (limited to 'src/backend/parser/parse_node.c')
0 files changed, 0 insertions, 0 deletions