2011/12/1 Kris Jurka <books(at)ejurka(dot)com>

>
>
> On Wed, 30 Nov 2011, Joel Jacobson wrote:
>
> > As you know, LISTEN/NOTIFY is broken in the Java client library. You
> have to
> > do a SELECT 1 in a while-loop to receive the notifications.
> >
> > http://jdbc.postgresql.org/documentation/head/listennotify.html
>
> This documentation is out of date.  Currently you can get notifications
> without polling the database if you are not using a SSL connection.  You
> still must poll the driver, using PGConnection.getNotifications, but it
> will return new notifications received without an intermediate database
> query.  This doesn't work over SSL and potentially some other connection
> types because it uses InputStream.available that not all
> implementations support.
>

I know it works without SSL, but we need SSL for this.

If it would be possible to fix it, my company is as I said willing to pay
for the cost of such a patch.


>
> Kris Jurka
>



-- 
Joel Jacobson
Trustly
+46703603801
https://trustly.com

In response to

• Re: Java LISTEN/NOTIFY client library work-around at 2011-12-01 00:55:13 from Kris Jurka

Responses

• Re: Java LISTEN/NOTIFY client library work-around at 2011-12-02 16:16:17 from Merlin Moncure

pgsql-hackers by date

Next:	From: Kohei KaiGai	Date: 2011-12-01 13:25:21
	Subject: Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement
Previous:	From: Greg Smith	Date: 2011-12-01 11:26:42
	Subject: Re: Patch to allow users to kill their own queries

pgsql-jdbc by date

Next:	From: Craig Ringer	Date: 2011-12-01 13:39:45
	Subject: Re: Bug: Cannot pass null in Parameter in Query for ISNULL
Previous:	From: Oliver Jowett	Date: 2011-12-01 09:38:04
	Subject: Re: Bug: Cannot pass null in Parameter in Query for ISNULL