Re: Automatic Client Failover - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Automatic Client Failover
Date
Msg-id 27737.1217905012@sss.pgh.pa.us
Whole thread Raw
In response to Re: Automatic Client Failover  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Automatic Client Failover  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> I think the proposal was for an extremely simple "works 75% of the time" 
> failover solution.  While I can see the attraction of that, the 
> consequences of having failover *not* work are pretty severe.

Exactly.  The point of failover (or any other HA feature) is to get
several nines worth of reliability.  "It usually works" is simply
not playing in the right league.

> On the other hand, we will need to deal with this for the built-in 
> replication project.

Nope, that's orthogonal.  A failover solution depends on having a master
and a slave database, but it has nothing directly to do with how those
DBs are synchronized.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Treat
Date:
Subject: Re: CommitFest July Over
Next
From: Tom Lane
Date:
Subject: Re: DROP DATABASE always seeing database in use