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 0EFF99DC9EF for ; Fri, 3 Mar 2006 14:10:10 -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 23006-09 for ; Fri, 3 Mar 2006 14:10:09 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from chilco.textdrive.com (chilco.textdrive.com [207.7.108.242]) by postgresql.org (Postfix) with ESMTP id B525F9DC984 for ; Fri, 3 Mar 2006 14:10:07 -0400 (AST) Received: from [192.168.1.109] (unknown [209.149.57.250]) by chilco.textdrive.com (Postfix) with ESMTP id D4776DC42B; Fri, 3 Mar 2006 18:10:54 +0000 (UTC) In-Reply-To: <1141408830.27729.512.camel@localhost.localdomain> References: <1141408830.27729.512.camel@localhost.localdomain> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: andy.shellam@mailnetwork.co.uk, pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit From: "Thomas F. O'Connell" Subject: Re: PITR as Online Backup Solution Date: Fri, 3 Mar 2006 12:10:00 -0600 To: Simon Riggs X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.421 required=5 tests=[AWL=0.421] X-Spam-Score: 0.421 X-Spam-Level: X-Archive-Number: 200603/43 X-Sequence-Number: 20800 On Mar 3, 2006, at 12:00 PM, Simon Riggs wrote: > 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 Auto failover is not a requirement for me. My primary goals are to reduce the need for pg_dump to occur nightly against a large production database and to reduce the window of potential data loss in a failover scenario, where the assumption is that the failover would be managed manually. There's too much application-inspired DDL and too many tables (as a result of an inheritance-heavy) data model for Slony to be a viable solution in the short term. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 3004 B Poston Avenue Nashville, TN 37203-1314 615-260-0005 (cell) 615-469-5150 (office) 615-469-5151 (fax)