From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | Mikko Tiihonen <mikko(dot)tiihonen(at)nitorcreations(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Connection-fail-over |
Date: | 2012-05-17 17:36:49 |
Message-ID: | CADK3HHJAMQjHky-1EaCN+3TzV_+AwUEMpKgPSqHUskG8XH1Kgw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Thu, May 17, 2012 at 1:23 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> On 17.05.2012 20:00, Mikko Tiihonen wrote:
>>
>> Hi,
>>
>> I have been thinking of adding connection fail-over support to the jdbc
>> driver. What this means is that there would be a way to specify more
>> than host:port pair to connect to. This will become handy with
>> high-availability installations.
>>
>> Currently the limitation of hostname means that there has to be a
>> virtual ip address that is moved with the active backend, which is a
>> complex solution that can break.
>>
>> If we have list of hostname:port pairs we just have to make sure that
>> only the master database allows connections from the jdbc clients.
>
>
> I'd suggest doing this as a generic wrapper or proxy that would work with
> any JDBC driver, not just PostgreSQL's. Maybe there is such a thing out
> there already? I believe many application servers at least can do that, and
> then there's http://ha-jdbc.sourceforge.net/, which I think can do that too.
>
I would agree with Heikki here that it makes more sense to have a
wrapper. I noticed that ha-jdbc has an lpgl license. How important is
it to have a bsd like license ?
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
From | Date | Subject | |
---|---|---|---|
Next Message | Kjetil Nygård | 2012-05-17 18:49:11 | Re: Java 1.4 |
Previous Message | Dave Cramer | 2012-05-17 17:25:41 | Re: Java 1.4 |