Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id A21309FB3AB for ; Thu, 7 Jun 2007 05:21:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 52415-09 for ; Thu, 7 Jun 2007 05:21:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id E50459FB7F3 for ; Thu, 7 Jun 2007 05:21:01 -0300 (ADT) Thread-Index: Aceo3NHPHMMCh3cvRY2VNThJTYAdPA== Received: from [192.168.0.4] ([85.211.203.94]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Jun 2007 04:21:16 -0400 Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826 Importance: normal Subject: Re: WAL restore From: "Simon Riggs" To: "Jerry Huff" Cc: In-Reply-To: <1181202636.26886.146.camel@silverbirch.site> References: <1181202636.26886.146.camel@silverbirch.site> Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 07 Jun 2007 09:19:09 +0100 Message-ID: <1181204349.26886.154.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Jun 2007 08:21:16.0546 (UTC) FILETIME=[D18F7620:01C7A8DC] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/63 X-Sequence-Number: 25731 On Thu, 2007-06-07 at 08:50 +0100, Simon Riggs wrote: > On Wed, 2007-06-06 at 23:31 -0700, Jerry Huff wrote: > > I am having a problem in restoring from WAL files. I have restored > > from a dump file and trying to step through the WAL files. > > > PANIC: syntax error in history file: START WAL LOCATION: 2/5DC04228 > > (file 00000001000000020000005D) > > Please send the history file, plus give your best understanding of the > previous history of this database's crashes/recoveries. AFAICS the .history contains the same contents as a normal .backup file would. Which is a little strange, so its either a definite bug or you're manually editing/manipulating file contents, which is unlikely to succeed. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com