Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id DC0509FB2CD for ; Fri, 6 Oct 2006 02:25:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 53912-08 for ; Fri, 6 Oct 2006 05:23:14 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 93AD39FB3B2 for ; Fri, 6 Oct 2006 02:23:14 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from webmail.enterprisedb.com (webmail.enterprisedb.com [63.246.7.176]) by svr4.postgresql.org (Postfix) with ESMTP id EB7FB5AF9AC for ; Fri, 6 Oct 2006 05:23:10 +0000 (GMT) Received: from [192.168.42.113] (natpool.bovine.net [67.100.216.14]) by webmail.enterprisedb.com (Postfix) with ESMTP id D9D0BA24E00; Fri, 6 Oct 2006 00:23:09 -0500 (CDT) In-Reply-To: <20061005184154.GE8826@phlogiston.dyndns.org> References: <20061005042417.87F0FC027@ogo.rapideye.de> <20061005184154.GE8826@phlogiston.dyndns.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <8689D509-4511-406B-AF5F-A245E2DC9008@enterprisedb.com> Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit From: Jim Nasby Subject: Re: postgres in HA constellation Date: Thu, 5 Oct 2006 20:43:21 -0500 To: Andrew Sullivan X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.478 tagged_above=0 required=5 tests=DATE_IN_PAST_03_06 X-Spam-Level: X-Archive-Number: 200610/37 X-Sequence-Number: 23340 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)