Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 558059FB50D for ; Mon, 23 Apr 2007 08:37:40 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 20110-10 for ; Mon, 23 Apr 2007 08:37:32 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail01.enterprisedb.com (webmail.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 570079FB503 for ; Mon, 23 Apr 2007 08:37:37 -0300 (ADT) thread-index: AceFm9ONMf5o/e3MT3OMlsca/kw3VQ== Received: from [172.24.32.16] ([62.232.55.118]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 23 Apr 2007 07:37:50 -0400 Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826 Subject: Re: pg_standby, Restartable Recovery after Hard Failure From: "Simon Riggs" To: "Thomas F. O'Connell" Cc: In-Reply-To: References: Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 23 Apr 2007 11:36:16 +0100 Message-ID: <1177324576.3650.198.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Apr 2007 11:37:50.0234 (UTC) FILETIME=[D28EAFA0:01C7859B] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/205 X-Sequence-Number: 25269 On Wed, 2007-04-18 at 18:11 -0500, Thomas F. O'Connell wrote: > Wanting a nice test of restartable recovery and pg_standby in a warm > standby server scenario I'm testing, today I pulled the plug on the > box where I was using Simon's test_warm_standby test harness. > Basically, in this scenario, I had one posgres cluster (primary) > against which pgbench was being run and a separate cluster (standby) > that had been created from a base backup and then put into continuous > recovery using pg_standby. In the middle of this scenario, I literally > pulled the plug. > If anyone can shed light on what might've happened in the hard failure > scenario, I'd be interested to know. I've kept the various archive, > primary, and standby directories created by test_warm_standby, so I > can report on any file contents. There is a possible error situation that I recently posted a fix to for 8.3. If you use the -k option with a low value then pg_standby can delete files from the archive too quickly, so that when it tries to return to the last restartpoint the file for that is missing. The fix posted passes a new %r parameter to pg_standby, allowing it to avoid deleting files too early. If that doesn't explain your situation please send me logfiles etc off-list so I can examine the details some more. Thanks. > It occurs to me that timestamp information might be nice to have in > pg_standby with debug mode. I might try patching pg_standby.c if no > one beats me to it. I'll look at doing this. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com