pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <jimn@enterprisedb.com>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: postgres in HA constellation
Date: Thu, 5 Oct 2006 20:43:21 -0500
Message-ID: <8689D509-4511-406B-AF5F-A245E2DC9008@enterprisedb.com> (raw)
In-Reply-To: <20061005184154.GE8826@phlogiston.dyndns.org>
References: <20061005042417.87F0FC027@ogo.rapideye.de>
	<20061005184154.GE8826@phlogiston.dyndns.org>

On Oct 5, 2006, at 1:41 PM, Andrew Sullivan wrote:
> On Thu, Oct 05, 2006 at 04:24:17AM -0000, Sebastian Reitenbach wrote:
>>
>> I just have one data center, no remote far away replication is  
>> needed.
>
> If it is at all feasible with your budget, I'd think _very strongly_
> about replicating using Slony inside your data centre _too_.  The
> shared storage answer is nice, but it is _really really really_ easy
> to shoot yourself in the foot with a rocket propelled grenade with
> that arrangement.  Very careful administration might prevent it, but
> there is a reason that none of the corporate people will guarantee
> two machines will never accidentally mount the same file system at
> once: in a shared-disc-only system, it's impossible to be 100%
> certain that the other machine really is dead and not coming back.
> Very tricky scripts could of course lower the risk.

Isn't it entirely possible that if the master gets trashed it would  
start sending garbage to the Slony slave as well?

I think PITR would be a much better option to protect against this,  
since you could probably recover up to the exact point of failover.

When it comes to the actual failover, take a look at the HA-linux  
project. They've got some stuff you could probably use (such as the  
heartbeat program). Another really good idea is to give the backup  
machine to kill the power to the primary machine, and not have either  
machine mount the shared storage at bootup.

If you're interested in paying someone to help setting this up, I  
know that we (EnterpriseDB) have folks that have done this before. I  
suspect that some of the other folks listed on the commercial support  
page have done this as well (likely Command Prompt and Varlena).
--
Jim Nasby                                    jimn@enterprisedb.com
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)





view thread (15+ messages)  latest in thread

Message-ID: <8689D509-4511-406B-AF5F-A245E2DC9008@enterprisedb.com>
Permalink:  ../8689D509-4511-406B-AF5F-A245E2DC9008@enterprisedb.com/
Also on:    postgresql.org/message-id/8689D509-4511-406B-AF5F-A245E2DC9008@enterprisedb.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jimn@enterprisedb.com, ajs@crankycanuck.ca
  Subject: Re: postgres in HA constellation
  In-Reply-To: <8689D509-4511-406B-AF5F-A245E2DC9008@enterprisedb.com>
  References: <20061005042417.87F0FC027@ogo.rapideye.de> <20061005184154.GE8826@phlogiston.dyndns.org> <8689D509-4511-406B-AF5F-A245E2DC9008@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox