Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 1043464FF57 for ; Mon, 25 Aug 2008 02:24:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 49387-01 for ; Mon, 25 Aug 2008 02:23:52 -0300 (ADT) X-Greylist: delayed 00:06:38.028513 by SQLgrey-1.7.6 Received: from web39702.mail.mud.yahoo.com (web39702.mail.mud.yahoo.com [209.191.106.48]) by postgresql.org (Postfix) with SMTP id BD3C964FF05 for ; Mon, 25 Aug 2008 02:23:53 -0300 (ADT) Received: (qmail 75107 invoked by uid 60001); 25 Aug 2008 05:17:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=Xc5MZmtaGcINxoyVWNpegR6VfB4QHnXasZRtwiSqGANV+Cn/IT1w6RDXtSDaMWMLNwfNTyKQJB71+2Z1eFiv2vR6nqPW63UL5jGTv0/UMl5QQKsXhI32lf6Lwnvudbh01bUu++hoM73+9te4/7sKsvi2psFQa9DKvm7fniXr5A8=; X-YMail-OSG: F0Za.ZkVM1m0CIA5FFNuZVXV6eoHJCvZxqHgJCGedCrrklmfVr7pbyM9aHbUanGdIa1Fg21iGesC0MnW..awtQS2kVY8YUR588LxAJDHPo_uy5aViBGeMvURzWHoqsaqpw-- Received: from [69.76.130.83] by web39702.mail.mud.yahoo.com via HTTP; Sun, 24 Aug 2008 22:17:12 PDT X-Mailer: YahooMailWebService/0.7.218.2 Date: Sun, 24 Aug 2008 22:17:12 -0700 (PDT) From: Bob Lunney Reply-To: bob_lunney@yahoo.com Subject: PITR wrm-standby startup fails To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <553812.74940.qm@web39702.mail.mud.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/147 X-Sequence-Number: 29992 I'm trying to vet the PITR/warm-standby process so set up a primary and secondary server on two different Windows machines. (Yeah, I know, but I don't have a choice in the matter.) The primary works fine and copies its WAL files to the archive directory. As long as the secondary is in recovery mode life is good. When I introduce the trigger file, however, to kick the secondary out of recovery mode it bombs, complaining that its looking for the next WAL file (which is never going to arrive, especially not in the local pg_xlog directory), then gives me an "invalid parameter" error. The relevent part of the secondary's log file is here: 2008-08-24 23:02:56 CDT LOG: restored log file "000000010000000400000088" from archive 2008-08-24 23:03:01 CDT LOG: restored log file "000000010000000400000089" from archive 2008-08-24 23:03:06 CDT LOG: restored log file "00000001000000040000008A" from archive 2008-08-24 23:07:02 CDT LOG: could not open file "pg_xlog/00000001000000040000008B" (log file 4, segment 139): No such file or directory 2008-08-24 23:07:05 CDT LOG: startup process (PID 1468) was terminated by exception 0xC000000D 2008-08-24 23:07:05 CDT HINT: See C include file "ntstatus.h" for a description of the hexadecimal value. 2008-08-24 23:07:05 CDT LOG: aborting startup due to startup process failure My recovery command is: restore_command = '..\bin\pg_standby -d -s 5 -t .\pgsql.trigger.5442 ..\data\archive %f %p %r 2>>pg_log\standby.log' I found this on the forums. Could it be the source of the problem I'm experiencing? Thanks in advance for the wizardly advice! Bob Lunney