From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, "Igal (at) Lucee(dot)org" <igal(at)lucee(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ian Barwick <ian(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: RETURNING primary_key() |
Date: | 2016-04-04 01:56:23 |
Message-ID: | 20160404015623.GR10850@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dave,
* Dave Cramer (pg(at)fastcrypt(dot)com) wrote:
> On 3 April 2016 at 15:35, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Not generally much of a JDBC user myself, but the inability to avoid
> > polling for LISTEN notifications is a pretty big annoyance, which I just
> > ran into with a client. I understand that -ng has a way to avoid that,
> > even for SSL connections.
>
> Yes, it is a custom api. Easy enough to add. Is this something of interest ?
I'd say that there is definite interest in this and there's a lot of
conversation about it on the interwebs (stackoverflow, etc).
My understanding is that the problem is actually with the SSL library
that the JDBC driver uses and that it basically lies about if there are
bytes available for reading (claiming that there never is by always
returning zero). The -ng driver, as I understand it, uses a newer SSL
library which better supports asking if there are bytes available to
read.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2016-04-04 02:13:50 | Re: Proposal: RETURNING primary_key() |
Previous Message | Michael Paquier | 2016-04-04 01:39:03 | Re: Recovery test failure for recovery_min_apply_delay on hamster |