| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | "Okano, Naoki" <okano(dot)naoki(at)jp(dot)fujitsu(dot)com> |
| Cc: | "pgsql-jdbc(at)lists(dot)postgresql(dot)org" <pgsql-jdbc(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: setPortNumber() should not be used when useing connection fail-over feature with PGConnectionPoolDataSource? |
| Date: | 2019-01-08 13:04:20 |
| Message-ID: | CADK3HH+n+1W-1F8wcnqf=_Etx-E5J0ZEOyFZxmOfEL5sAe7cMA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
On Tue, 8 Jan 2019 at 03:09, Okano, Naoki <okano(dot)naoki(at)jp(dot)fujitsu(dot)com>
wrote:
> Dave Cramer [mailto:pg(at)fastcrypt(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2019-01-10 16:27:27 | PGCopyOutputStream close() v. endCopy() |
| Previous Message | Okano, Naoki | 2019-01-08 08:09:02 | RE: setPortNumber() should not be used when useing connection fail-over feature with PGConnectionPoolDataSource? |