From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Automatic Client Failover |
Date: | 2008-08-15 18:25:56 |
Message-ID: | 200808151825.m7FIPu820739@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs wrote:
> > > Implementation would be to make PQreset() try secondary connection if
> > > the primary one fails to reset. Of course you can program this manually,
> > > but the feature is that you wouldn't need to, nor would you need to
> > > request changes to 27 different interfaces either.
> >
> > I assumed share/pg_service.conf would help in this regard; place the
> > file on a central server and modify that so everyone connects to another
> > server. Perhaps we could even add round-robin functionality to that.
>
> I do want to keep it as simple as possible, but we do need a way that
> will work without reconfiguration at the time of danger. It needs to be
> preconfigured and tested, then change controlled so we all know it
> works.
OK, so using share/pg_service.conf as an implementation example, how
would this work? The application supplies multiple service names and
libpq tries attaching to each one in the list until one works?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2008-08-15 19:24:44 | Re: proposal sql: labeled function params |
Previous Message | Hannu Krosing | 2008-08-15 18:20:47 | Re: proposal sql: labeled function params |