Automatic Client Failover - Mailing list pgsql-hackers

From Simon Riggs
Subject Automatic Client Failover
Date
Msg-id 1217884116.3934.558.camel@ebony.t-mobile.de.
Whole thread Raw
Responses Re: Automatic Client Failover  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Re: Automatic Client Failover  (Josh Berkus <josh@agliodbs.com>)
Re: Automatic Client Failover  (Hannu Krosing <hannu@krosing.net>)
Re: Automatic Client Failover  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
When primary server fails, it would be good if the clients connected to
the primary knew to reconnect to the standby servers automatically.

We might want to specify that centrally and then send the redirection
address to the client when it connects. Sounds like lots of work though.

Seems fairly straightforward to specify a standby connection service at
client level: .pgreconnect, or pgreconnect.conf
No config, then option not used.

Would work with various forms of replication.

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.

Good? Bad? Ugly? 

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Mini improvement: statement_cost_limit
Next
From: Robert Treat
Date:
Subject: Re: Mini improvement: statement_cost_limit