From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | Ravi Krishna <sravikrishna3(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Automatic Client routing |
Date: | 2015-06-05 02:02:51 |
Message-ID: | 20150604220251.920d6b5f2a44658e6f6df045@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 4 Jun 2015 08:53:15 -0400
Ravi Krishna <sravikrishna3(at)gmail(dot)com> wrote:
> Are there any plans to introduce the concept of automatic client
> routing to the principal server in a cluster of N machines. For
> example, if there is a four node replication cluster N1 .. N4, at any
> time only one can be principal (the one which does the writing). In
> Oracle and DB2, client side libraries provide a way for the clients to
> connect to the principal writer regardless of where it is running on
> N1 .. N4. This way client need to be aware of only one connection
> string.
>
> EnterpriseDb is a failover manager which relies on virtual IP
> management, not the one I described above.
pgpool has this capacity.
--
Bill Moran <wmoran(at)potentialtech(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Konoplev | 2015-06-05 02:32:42 | Re: replicating many to one |
Previous Message | Thomas Munro | 2015-06-05 01:47:12 | Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |