Automatic Client routing

From: Ravi Krishna <sravikrishna3(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Automatic Client routing
Date: 2015-06-04 12:53:15
Message-ID: CACER=P3RCh-0+K5cUynuv=EXEXGEe+O0zuA59nEYLcL4478bqA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marc Mamin 2015-06-04 13:01:23 Re: Row visibility issue with consecutive triggers, one being DEFERRED
Previous Message Marc Mamin 2015-06-04 10:27:11 Re: pg_relation_size performance issue