Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id DED869FB933 for ; Fri, 29 Jun 2007 10:46:00 -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 93872-07 for ; Fri, 29 Jun 2007 10:45:56 -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 170869FB849 for ; Fri, 29 Jun 2007 10:45:56 -0300 (ADT) thread-index: Ace6U9ouyv0qrnpaSt2J+iC0obbFmQ== Received: from [172.24.32.50] ([62.232.55.118]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 29 Jun 2007 09:46:10 -0400 Subject: Re: missing history file Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4073 From: "Simon Riggs" To: "George Wilk" Cc: In-Reply-To: <008401c7ba44$5efa4170$0d7ba8c0@ellacoya.com> References: <008401c7ba44$5efa4170$0d7ba8c0@ellacoya.com> Content-Type: text/plain; charset="utf-8" Date: Fri, 29 Jun 2007 14:41:53 +0100 Message-ID: <1183124513.3589.104.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 29 Jun 2007 13:46:10.0515 (UTC) FILETIME=[D9F59230:01C7BA53] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/297 X-Sequence-Number: 25965 On Fri, 2007-06-29 at 07:55 -0400, George Wilk wrote: > My warm standby server is looking for a history file when booting up. > It is looking for 00000001.history file to be exact.=20 Just ignore 00000001. Recovery will work fine even if absent. Don't ignore all history files though, just that one. Hmmm, come to think of it, why is it requesting it at all? We should just skip that request. > Since my *live* server doesn=E2=80=99t produce such file, I create an em= pty > 00000001.history file in the archive directory and that seems to > satisfy this requirement allowing the standby server to come up in the > recovery mode. =20 Well, that should at least generate a message that says "history file empty, using targetTLI". > It would be nice to know though how such file is created. I know that > the *live* server creates *.backup file as a result of > pg_stop_backup() command and this file is accurately archived on the > standby server. Should I be renaming this file, or is there some > other mechanism to tell my standby server what the history file is? The timeline history file is only required when you do a recovery of a system that has itself already undergone a PITR. Have a look at pg_standby, accessible via CVS in contrib/pg_standby. --=20 Simon Riggs =20 EnterpriseDB http://www.enterprisedb.com