From: | Maciek Sakrejda <maciek(at)heroku(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Client deadlocks when connecting via ssl |
Date: | 2015-01-25 20:33:04 |
Message-ID: | CAKwe89DRPxibMs0PmnC1bNuT77EoJ7Ywsdq2W==JLX0KGeNBww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
Thanks,
Maciek
[1]: http://www.postgresql.org/message-id/5436991B.5020708@vmware.com
[2]:
http://blog.maestropublishing.com/2015/01/16/gunicorn-dyno-death-spiral-on-heroku-part-ii/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-01-25 20:40:10 | Re: longjmp clobber warnings are utterly broken in modern gcc |
Previous Message | Greg Stark | 2015-01-25 20:24:32 | Re: longjmp clobber warnings are utterly broken in modern gcc |