Re: Deadlock in libpq

On Thu, Mar 24, 2011 at 16:43, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> He needs to rule out the most obvious problem first -- PQInitSSL being
> called improperly or at the wrong time.  OP: It's a library wide
> setting and must be called before the first connection is established
> and only once.  Perhaps the HDBC driver has some bad logic there.

I just grepped the source, and PQInitSSL doesn't appear once. So I
think it is never called at all. I'll try adding it to our application
startup code, and see if that fixes the problem.

This doesn't explain the broken connections without SSL though. I
think if my threads were dying, I'd see a log message: there are top
level exception handlers that log to email, file and the console. The
connection code also has a handler that closes the connection in case
of an exception.

--
Erik Hesselink
http://silkapp.com