Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 990F69FB518 for ; Fri, 29 Jun 2007 08:55:34 -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 01028-06 for ; Fri, 29 Jun 2007 08:55:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mail02.ellacoya.com (67-135-29-172.dia.static.qwest.net [67.135.29.172]) by postgresql.org (Postfix) with ESMTP id 6625C9FB4FA for ; Fri, 29 Jun 2007 08:55:24 -0300 (ADT) Received: from YZANGXP ([192.168.123.13]) by mail02.ellacoya.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jun 2007 07:55:23 -0400 From: "George Wilk" To: Subject: missing history file Date: Fri, 29 Jun 2007 07:55:21 -0400 Message-ID: <008401c7ba44$5efa4170$0d7ba8c0@ellacoya.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0085_01C7BA22.D7E8A170" X-Mailer: Microsoft Office Outlook 11 Thread-Index: Ace6RF7WCss5CftAQHmCVtd17KHvIA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-OriginalArrivalTime: 29 Jun 2007 11:55:23.0973 (UTC) FILETIME=[604FBF50:01C7BA44] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1021-15266.003 X-TM-AS-Result: No--7.880800-4.000000-31 X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/296 X-Sequence-Number: 25964 This is a multi-part message in MIME format. ------=_NextPart_000_0085_01C7BA22.D7E8A170 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit My warm standby server is looking for a history file when booting up. It is looking for 00000001.history file to be exact. Since my *live* server doesn't produce such file, I create an empty 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. 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? Thanks in advance, ~george ------=_NextPart_000_0085_01C7BA22.D7E8A170 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

My warm standby server is looking for a history file = when booting up.  It is looking for 00000001.history file to be = exact.  Since my *live* server = doesn’t produce such file, I create an empty 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.  =

 

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?

 

Thanks in advance,

~george

------=_NextPart_000_0085_01C7BA22.D7E8A170--