Re: Client deadlocks when connecting via ssl

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Maciek Sakrejda <maciek(at)heroku(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Client deadlocks when connecting via ssl
Date: 2015-01-26 07:13:34
Message-ID: 54C5E91E.9050609@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Maciek Sakrejda 2015-01-26 07:37:42 Re: Client deadlocks when connecting via ssl
Previous Message Michael Paquier 2015-01-26 06:32:51 Re: Error check always bypassed in tablefunc.c