Re: setPortNumber() should not be used when useing connectionfail-over feature with PGConnectionPoolDataSource? - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: setPortNumber() should not be used when useing connectionfail-over feature with PGConnectionPoolDataSource?
Date
Msg-id CADK3HH+n+1W-1F8wcnqf=_Etx-E5J0ZEOyFZxmOfEL5sAe7cMA@mail.gmail.com
Whole thread Raw
In response to RE: setPortNumber() should not be used when useing connectionfail-over feature with PGConnectionPoolDataSource?  ("Okano, Naoki" <okano.naoki@jp.fujitsu.com>)
List pgsql-jdbc
To be honest, we've not put a lot of work into pooling implementations as there are far better ones out there.

That being said, there aren't good ones that do automatic failover so perhaps there is some utility in it



On Tue, 8 Jan 2019 at 03:09, Okano, Naoki <okano.naoki@jp.fujitsu.com> wrote:
Dave Cramer [mailto:pg@fastcrypt.com] wrote:
> Pretty sure this was never intended to work.
>
>
> That said if you can provide a pull request we can look at implementing it.

Thank you for your reply!
I understand it does not work as intended.
So, I try to implement it and will send a pull request.

Regards,
Okano Naoki

pgsql-jdbc by date:

Previous
From: "Okano, Naoki"
Date:
Subject: RE: setPortNumber() should not be used when useing connectionfail-over feature with PGConnectionPoolDataSource?
Next
From: Rob Sargent
Date:
Subject: PGCopyOutputStream close() v. endCopy()