Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 505EE9FA5DC for ; Wed, 11 Oct 2006 11:42:29 -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 36754-02 for ; Wed, 11 Oct 2006 11:42:26 -0300 (ADT) 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 0E6F19FB251 for ; Wed, 11 Oct 2006 11:42:25 -0300 (ADT) Received: by ogo.rapideye.de (Postfix, from userid 1000) id 3F4538C03F; Wed, 11 Oct 2006 16:42:23 +0200 (CEST) organization: RapidEye AG X-Mailer: OpenGroupware.org MIME-Version: 1.0 from: "Sebastian Reitenbach" Subject: Re: postgres in HA constellation to: pgsql-admin@postgresql.org reply-to: "Sebastian Reitenbach" content-type: text/plain; charset="us-ascii" date: Wed, 11 Oct 2006 14:42:22 -0000 content-transfer-encoding: 7bit Message-Id: <20061011144223.3F4538C03F@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/82 X-Sequence-Number: 23385 Hi, > > I think this highlights exactly what I'm trying to emphasise: in > actual, shared-nothing systems like this, there's no possible > guarantee of "never". There are possible guarantees of "very > rarely". The problem is, you're already trying to address a teeny > portion of the likely events on your machines. So you have to assume > that more than one thing might break at the same time, and have a > recovery plan for it. I submit that a recovery plan of "restore from > pg_dump" is usually not going to be enough if it was worth the cost > and hassle of setting up shared disk failover. YMMV, of course. > yes, I did a restore from a dump with pg_dump, that took over a day. maybe I can speed it up a bit, but this is going to take too long. Sebastian