Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 1E2369FA5E9 for ; Thu, 5 Oct 2006 15:42:06 -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 47949-10 for ; Thu, 5 Oct 2006 18:42:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by postgresql.org (Postfix) with ESMTP id E08E09FA372 for ; Thu, 5 Oct 2006 15:42:00 -0300 (ADT) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=phlogiston.dydns.org) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1GVYSf-0005L7-Ap for pgsql-admin@postgresql.org; Thu, 05 Oct 2006 15:00:49 -0400 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 386464172; Thu, 5 Oct 2006 14:41:54 -0400 (EDT) Date: Thu, 5 Oct 2006 14:41:54 -0400 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: postgres in HA constellation Message-ID: <20061005184154.GE8826@phlogiston.dyndns.org> References: <20061005042417.87F0FC027@ogo.rapideye.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061005042417.87F0FC027@ogo.rapideye.de> User-Agent: Mutt/1.5.9i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.135 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200610/32 X-Sequence-Number: 23335 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. If you're really going to have all that data, it's going to be a major pain to restore in the event of such corruption. In addition, your recovery will only be to the last dump. That's why I suggest replicating, either with Slony or something else, as a belt that will nicely complement the suspenders of your shared-disc failover. A -- Andrew Sullivan | ajs@crankycanuck.ca I remember when computers were frustrating because they *did* exactly what you told them to. That actually seems sort of quaint now. --J.D. Baldwin