David Ford writes: > Libpq doesn't deal with system calls being interrupted in the slightest. > None of the read/write or socket calls handle any errors. Even benign > returns i.e. EINTR are treated as fatal errors and returned. Not to > malign, but there is no reason not to continue on and handle EINTR.
Libpq certainly does deal with system calls being interrupted: It does not allow them to be interrupted. Take a look into the file pqsignal.c to see why. If your alarm timer interrupts system calls then that's because you have installed your signal handler to allow that. In my mind, a reasonable behaviour in that case would be to let the PQconnect or equivalent fail and provide the errno to the application. -- Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
