On 4 April 2016 at 10:13, Dave Cramer <p...@fastcrypt.com> wrote:

> Async notification is the easier part, I wasn't aware that the ssl library
> had this problem though
AFAIK the issue is that even if there are bytes available on the underlying
socket, the SSL lib doesn't know if that means there are bytes readable
from the wrapped SSL socket. The traffic on the underlying socket could be
renegotiation messages or whatever.

We really need non-blocking reads.

 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Reply via email to