Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id BB7379FB3FC for ; Fri, 6 Oct 2006 03:37: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 75642-01 for ; Fri, 6 Oct 2006 06:35:28 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from ogo.rapideye.de (ogo.rapideye.de [212.204.56.174]) by postgresql.org (Postfix) with ESMTP id BEBF89FB407 for ; Fri, 6 Oct 2006 03:34:26 -0300 (ADT) Received: by ogo.rapideye.de (Postfix, from userid 1000) id 49239C01C; Fri, 6 Oct 2006 08:34:25 +0200 (CEST) organization: RapidEye AG cc: pgsql-admin@postgresql.org X-Mailer: OpenGroupware.org MIME-Version: 1.0 from: "Sebastian Reitenbach" Subject: Re: postgres in HA constellation reply-to: "Sebastian Reitenbach" content-type: text/plain; charset="us-ascii" date: Fri, 06 Oct 2006 06:34:25 -0000 content-transfer-encoding: 7bit Message-Id: <20061006063425.49239C01C@ogo.rapideye.de> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200610/38 X-Sequence-Number: 23341 Hi all, > > 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. As I am using carp on OpenBSD to setup HA cluster, I am very comfortable with ucarp, the userland implementation for Linux. at boot up the default mount of the database files is readonly and having the database not running, then starting ucarp, and then only in case this machine becomes master, it remounts the postgres data and shall start the database. And I thought about that killing the power of the "lost" master after a takeover too, to make sure hte machine will not come back unconditionally later. kind regards Sebastian