Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 166932E49D9 for ; Fri, 11 Jan 2008 17:08:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 85997-01 for ; Fri, 11 Jan 2008 17:08:00 -0400 (AST) Received: from mail2.yozons.com (mail2.yozons.com [63.251.168.97]) by postgresql.org (Postfix) with ESMTP id C09802E49C3 for ; Fri, 11 Jan 2008 17:08:02 -0400 (AST) Received: from [192.168.1.2] (pool-71-164-18-27.sttlwa.fios.verizon.net [71.164.18.27]) (authenticated bits=0) by mail2.yozons.com (8.12.10/8.12.10) with ESMTP id m0BL81lG026796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 11 Jan 2008 13:08:01 -0800 Message-ID: <4787DAB4.9020402@computer.org> Date: Fri, 11 Jan 2008 13:08:04 -0800 From: David Wall Reply-To: d.wall@computer.org User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: WAL recovery, stop and resume recovery? References: <4787C7A7.3000503@computer.org> <24388.1200083631@sss.pgh.pa.us> In-Reply-To: <24388.1200083631@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/126 X-Sequence-Number: 27900 > No. Once you've done any transactions in the backup DB, its transaction > history has diverged from the master and you can't resume tracking the > master. It shouldn't even let you try --- what shenanigans did you pull > to force it back into recovery mode? > Well, I didn't think it was shenanigans, I just stopped the database once it completed the first recovery, ran a few queries, then re-installed the recovery.conf and started it back up like I initially did. I figured this could be an issue, but since I hadn't issued any changes, I had hoped it might work. > There's some work being done on allowing read-only queries against an > in-recovery database, which I think would satisfy your desire to see if > the backup were sane or not. But I wouldn't bet money on that getting > into the system anytime soon. It's definitely not something you can > cobble up from spare parts. > Fair enough. It's probably not a big deal as I'm doing this only because we're new to using WAL copying for a warm standby, and of course we're testing to see that rows inserted, removed, updated, tables added and dropped, indexes added and dropped, etc. are all making it through. It appears that this works like a charm! Is there a way to know how many WAL files I should keep around to ensure I can recover back to a valid primary checkpoint without having to redo the entire backup process on the primary in 8.2, or do I just have to wait for 8.3 and %r option for recovery? Thanks, David