X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 57BF09DC97F for ; Fri, 3 Mar 2006 14:00:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 22125-09 for ; Fri, 3 Mar 2006 14:00:41 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by postgresql.org (Postfix) with ESMTP id 2225A9DC951 for ; Fri, 3 Mar 2006 14:00:39 -0400 (AST) Received: from [192.168.0.5] (unknown [84.12.26.47]) by smtp.nildram.co.uk (Postfix) with ESMTP id 0F6452591F7; Fri, 3 Mar 2006 18:00:36 +0000 (GMT) Subject: Re: PITR as Online Backup Solution From: Simon Riggs To: andy.shellam@mailnetwork.co.uk Cc: "'Thomas F. O'Connell'" , pgsql-admin@postgresql.org In-Reply-To: References: Content-Type: text/plain Date: Fri, 03 Mar 2006 18:00:30 +0000 Message-Id: <1141408830.27729.512.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.091 required=5 tests=[AWL=0.091] X-Spam-Score: 0.091 X-Spam-Level: X-Archive-Number: 200603/41 X-Sequence-Number: 20798 On Fri, 2006-03-03 at 10:23 +0000, Andy Shellam wrote: > Then you would have to find a method of telling the script > that you wish to bring the database up and it will exit and allow PGSQL to > come up at the current state with the latest data. > Replication sounds like a better option If you want auto failover, then you will need a package that detects that accurately and can initiate any required actions, whatever method you choose of keeping multiple systems in sync. IMHO auto failover needs *extensive* testing and failure analysis to make it more robust and practically useful than manual failover, so is not quite the magic bullet it may appear. Best Regards, Simon Riggs