Re: Client deadlocks when connecting via ssl

On 01/25/2015 10:33 PM, Maciek Sakrejda wrote:

Hello,

I wanted to follow up on a bug report [1] from October. In a reply, Heikki
conceded that there does seem to be an issue with how Postgres interacts
with OpenSSL, but the nature of the API makes it difficult to fix.

I'm with Heroku Postgres, and though the issue is not Heroku-specific, it
does seem to affect a lot of our customers, especially ones using the
Python Gunicorn web server. One particular account of this is written up in
a blog post [2]. It's a frustrating issue that's rather hard to diagnose.

Is there anything we can do to help resolve this? Are there any recommended
workarounds?

I couldn't come up with any good solutions. I would suggest speaking to
the OpenSSL folk. They must be aware of the issue, so what do they
recommend, do they have any plans to fix it, and if there's anything you
can do to help them.

- Heikki

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Sun, Jan 25, 2015 at 11:13 PM, Heikki Linnakangas <
hlinnakangas@vmware.com> wrote:

I couldn't come up with any good solutions. I would suggest speaking to
the OpenSSL folk. They must be aware of the issue, so what do they
recommend, do they have any plans to fix it, and if there's anything you
can do to help them.

Thanks. We'll give that a shot.