Re: Proposal: RETURNING primary_key() - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: Proposal: RETURNING primary_key()
Date
Msg-id CADK3HHLVcQqV8TXjRO=rebba3VemncfCWJHpCOWRDTGzt_BseA@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: RETURNING primary_key()  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Proposal: RETURNING primary_key()  (Craig Ringer <craig@2ndquadrant.com>)
Re: Proposal: RETURNING primary_key()  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 3 April 2016 at 21:56, Stephen Frost <sfrost@snowman.net> wrote:
Dave,

* Dave Cramer (pg@fastcrypt.com) wrote:
> On 3 April 2016 at 15:35, Stephen Frost <sfrost@snowman.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.


Hmmm. that complicates things...

Async notification is the easier part, I wasn't aware that the ssl library had this problem though





pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Proposal: RETURNING primary_key()
Next
From: Craig Ringer
Date:
Subject: Re: Proposal: RETURNING primary_key()