Re: Deadlock in libpq

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Erik Hesselink <hesselink(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Deadlock in libpq
Date: 2011-03-24 15:00:44
Message-ID: 24628.1300978844@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> *something* must be initializing ssl, or you can't make secure
> connections from libpq. you need to find out which pq ssl init
> function is begin called, when it is being called, and with what
> arguments. One of the main things PQInitSSL does is set up a lock
> vector which it passes to the crypto library. The fact you are having
> blocking issues around those locks is suggesting SSL was not set up
> properly, something happened after being set up so that the locks are
> no longer good, you have application thread issue (although that
> sounds unlikely), or (least likely worst case) there is a bug in
> crypto.

Given that Erik still sees trouble when not using SSL, my money would
be on the idea that somewhere he's got two threads trying to use the
same connection object concurrently. The SSL confusion is just one
symptom of that.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2011-03-24 15:08:22 Re: Problem calling setweight function from JDBC
Previous Message Tom Lane 2011-03-24 14:52:24 Re: constraint partition issue