Re: Core team statement on replication in PostgreSQL - Mailing list pgsql-hackers

From Andreas 'ads' Scherbaum
Subject Re: Core team statement on replication in PostgreSQL
Date
Msg-id 20080530162653.3a243dd6@iridium.wars-nicht.de
Whole thread Raw
In response to Re: Core team statement on replication in PostgreSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 29 May 2008 18:29:01 -0400 Tom Lane wrote:

> Dimitri Fontaine <dim@hi-media.com> writes:
> > While at it, would it be possible for the "simple" part of the core  
> > team statement to include automatic failover?
> 
> No, I think it would be a useless expenditure of energy.  Failover
> includes a lot of things that are not within our purview: switching
> IP addresses to point to the new server, some kind of STONITH solution
> to keep the original master from coming back to life, etc.  Moreover
> there are already projects/products concerned with those issues.

True words. Failover is not and should not be part of PostgreSQL.

But PG can help the failover solution, as example: an easy-to-use
interface about the current slave status comes into my mind. Other
ideas might also be possible.


> It might be useful to document where to find solutions to that problem,
> but we can't take it on as part of core Postgres.

Ack


Kind regards

--             Andreas 'ads' Scherbaum
German PostgreSQL User Group


pgsql-hackers by date:

Previous
From: Robert Hodges
Date:
Subject: Re: replication hooks
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: Initial max_connections for initdb on FreeBSD.