Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id F3F0E9FC2FB for ; Fri, 29 Jun 2007 12:22:12 -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 26528-06 for ; Fri, 29 Jun 2007 12:22:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail02.ellacoya.com (67-135-29-172.dia.static.qwest.net [67.135.29.172]) by postgresql.org (Postfix) with ESMTP id E3D789FC328 for ; Fri, 29 Jun 2007 12:22:06 -0300 (ADT) Received: from YZANGXP ([192.168.123.13]) by mail02.ellacoya.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 29 Jun 2007 11:22:06 -0400 From: "George Wilk" To: Subject: Re: missing history file Date: Fri, 29 Jun 2007 11:22:03 -0400 Message-ID: <00d201c7ba61$3f078540$0d7ba8c0@ellacoya.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <12838.1183128750@sss.pgh.pa.us> Thread-Index: Ace6XUZyb1PY2+KwQFGxYdoLZsx+TwAA8lLQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-OriginalArrivalTime: 29 Jun 2007 15:22:06.0195 (UTC) FILETIME=[409CA430:01C7BA61] X-TM-AS-Product-Ver: SMEX-8.0.0.1181-5.000.1021-15266.003 X-TM-AS-Result: No--8.267300-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/302 X-Sequence-Number: 25970 Tom, When and by what process is the history file being created? My standby server seems to be looking for it when put back in the recovery mode, after functioning as primary for a while. How should I handle missing history file in my script? Cheers, ~george -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Friday, June 29, 2007 10:53 AM To: Simon Riggs Cc: George Wilk; pgsql-admin@postgresql.org Subject: Re: [ADMIN] missing history file "Simon Riggs" writes: > 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. No, because then people would misdesign their recovery scripts to not be able to deal with not finding a history file. As things are, they will certainly be exposed to that case in any testing they do. If we optimize this call away, then they won't see the case until they're in very deep doo-doo. regards, tom lane