Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 316719FB351 for ; Wed, 4 Oct 2006 12:33:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 78154-06 for ; Wed, 4 Oct 2006 12:33:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from wolff.to (wolff.to [66.93.197.194]) by postgresql.org (Postfix) with SMTP id C160F9FB34F for ; Wed, 4 Oct 2006 12:32:58 -0300 (ADT) Received: (qmail 24951 invoked by uid 500); 4 Oct 2006 15:43:18 -0000 Date: Wed, 4 Oct 2006 10:43:18 -0500 From: Bruno Wolff III To: Sebastian Reitenbach Cc: pgsql-admin@postgresql.org Subject: Re: postgres in HA constellation Message-ID: <20061004154318.GB23343@wolff.to> Mail-Followup-To: Bruno Wolff III , Sebastian Reitenbach , pgsql-admin@postgresql.org References: <20061004112345.496B6C01A@ogo.rapideye.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061004112345.496B6C01A@ogo.rapideye.de> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.044 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200610/23 X-Sequence-Number: 23326 On Wed, Oct 04, 2006 at 11:23:45 -0000, Sebastian Reitenbach wrote: > > something I thought that might work: > is there sth. that will repair an inconsisten postgresql datastore? e.g. the > master database died, the slave will mount the storage, then repair it in a > reasonable time, and then start to work. You can just start the slave server and it will recover using th WAL files and should do so in a short time. However, you MUST be certain that the master is no longer running when the slave starts or your database WILL BE TRASHED. > > are there any other possibilities that might work that I am not aware of? > anybody has experiences with postgres in a HA environment with shared storage? You can also use servers with redundant hardware (hotplug CPUs and the like) to make failure less likely. If you get the hardware failure rates down to that of your storage system, that might be good enough for your purposes. If you have multiple data centers to protect against disaster, then you might look at SLONY which you can use to replicate to a slave system. However, I think it is possible for the master to report a transaction as commited before it is shipped off to the slave, so that if the master fails you might lose some transactions when switching to the slave. But double check with the SLONY documentation on this.