Re: Proposal: RETURNING primary_key()
От | Dave Cramer |
---|---|
Тема | Re: Proposal: RETURNING primary_key() |
Дата | |
Msg-id | CADK3HHLhqAEzW0mQ1uHJeMJUsTiED6-zh1nTABjZwLEW2=E5yw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Proposal: RETURNING primary_key() (Stephen Frost <sfrost@snowman.net>) |
Список | pgsql-hackers |
On 3 April 2016 at 22:20, Stephen Frost <sfrost@snowman.net> wrote:
* Craig Ringer (craig@2ndquadrant.com) wrote:
> On 4 April 2016 at 10:13, Dave Cramer <pg@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.
That would certainly be a good way to address this, but I'm guessing
it's non-trivial to implement.
AFAICT, the ng driver still has to generate traffic as well.
Thanks!
Stephen
В списке pgsql-hackers по дате отправления: