Bruce Momjian <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> Bruce Momjian <[EMAIL PROTECTED]> writes: >>> ! if (SOCK_ERRNO != ECONNRESET) >>> ! SSL_shutdown(conn->ssl); >> >> Ummm ... what is this supposed to fix exactly, and what are the odds
> I think the user was getting SIGPIPE on SSL_shutdown() of a closed > connection. It seems moderately improbable that by the time control arrives here, errno still has anything to do with the last operation on the SSL socket. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate