X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 6F04D9DCC61 for ; Wed, 22 Mar 2006 09:33:28 -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 49330-02 for ; Wed, 22 Mar 2006 09:33:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id C41579DCC2D for ; Wed, 22 Mar 2006 09:33:25 -0400 (AST) Received: by noel.decibel.org (Postfix, from userid 1001) id 8B10256431; Wed, 22 Mar 2006 07:33:29 -0600 (CST) Received: (hashcash-sendmail, from uid 1001); Wed, 22 Mar 2006 07:33:28 -0600 Date: Wed, 22 Mar 2006 07:33:28 -0600 From: "Jim C. Nasby" To: "Thomas F. O'Connell" Cc: pgsql-docs@postgresql.org Subject: Re: Online Backups: Minor Caveat, Major Addition? Message-ID: <20060322133328.GE15742@pervasive.com> References: <42D1F5FC-42DD-49D8-8509-0D68C5B9384C@sitening.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42D1F5FC-42DD-49D8-8509-0D68C5B9384C@sitening.com> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060322:tfo@sitening.com::HCFJME1zDrJWcxG8:0DAsL X-Hashcash: 1:20:060322:pgsql-docs@postgresql.org::luwk5wPuh0HuwpAy:000000000000 00000000000000000000000008vQ X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.108 required=5 tests=[AWL=0.108] X-Spam-Score: 0.108 X-Spam-Level: X-Archive-Number: 200603/26 X-Sequence-Number: 3483 On Mon, Mar 20, 2006 at 09:54:53AM -0600, Thomas F. O'Connell wrote: > 23.3.3.1 - Inline (or In-place) Recovery > 23.3.3.2 - Remote Recovery or Recovery into a New Cluster > 23.3.3.3 - Continuous Recovery > > The "Inline Recovery" section would just be the existing 23.3.3 > repurposed. > > The "Remote/New Cluster Recovery" section would be an edited version > of the existing 23.3.3 to eliminate step1 and include the note > suggested above. > > The "Continuous Recovery" section would include details of how to > continuously apply WAL files to a separate cluster in order to have a > true hot standby system. > > Thoughts? > > I'd be happy to draft 23.3.3.2. I'll have to figure out how to > implement Simon Riggs's suggestion of a wait-for-files > recover_command including a way to interrupt in the event of a need > for actual failover-style recovery before I could draft 23.3.3.3, > though. BTW, when it comes to continuous recovery you should have a look at http://pgfoundry.org/projects/pgpitrha/ -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461