Skip site navigation (1) Skip section navigation (2)

Re: Sync Rep Design

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Robert Treat <rob(at)xzilla(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Sync Rep Design
Date: 2010-12-31 08:15:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 12/30/2010 10:27 PM, Simon Riggs wrote:
> On Thu, 2010-12-30 at 22:08 +0100, Stefan Kaltenbrunner wrote:
>> On 12/30/2010 10:01 PM, Simon Riggs wrote:
>>> On Thu, 2010-12-30 at 15:51 -0500, Robert Treat wrote:
>>>> Still, one thing that has me concerned is that in the case of two
>>>> slaves, you don't know which one is the more up-to-date one if you
>>>> need to failover. It'd be nice if you could just guarantee they both
>>>> are...
>>> Regrettably, nobody can know that, without checking.
>> how exactly would you check? - this seems like something that needs to
>> be done from the SQL and the CLI level and also very well documented
>> (which I cannot see in your proposal).
> This is a proposal for sync rep, not multi-node failover. I'm definitely
> not going to widen the scope of this project.
> Functions already exist to check the thing you're asking.

well your proposal includes a lot of stuff on how to avoid dataloss and 
getting High Availability - so I think it is a requirement for us to 
tell the DBA what the procedures are for both setting it up (which is 
what is in the docs - but only 50% of the thing) and what to do in the 
case of a desaster (which is the other part of the problem).
Or said otherwise - sync rep is not very useful if there is no easy and 
reliable way to get that information, if that stuff is already available 
even better but I'm not aware of what is there and what not, so I expect 
others to have the same problem.


In response to

pgsql-hackers by date

Next:From: Stefan KaltenbrunnerDate: 2010-12-31 08:27:29
Subject: Re: Sync Rep Design
Previous:From: Hannu KrosingDate: 2010-12-31 07:50:43
Subject: Re: Sync Rep Design

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group