Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 755F89FC394 for ; Fri, 29 Jun 2007 14:45:50 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 36470-04 for ; Fri, 29 Jun 2007 14:45:30 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by postgresql.org (Postfix) with ESMTP id 678049FC245 for ; Fri, 29 Jun 2007 14:45:42 -0300 (ADT) Received: from Courts-MTA by gwmta.wicourts.gov with Novell_GroupWise; Fri, 29 Jun 2007 12:45:41 -0500 Message-Id: <4684FEE7.EE98.0025.0@wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 7.0.2 Date: Fri, 29 Jun 2007 12:45:27 -0500 From: "Kevin Grittner" To: "Tom Lane" Cc: "George Wilk" , Subject: Re: missing history file References: <00d201c7ba61$3f078540$0d7ba8c0@ellacoya.com><00d201c7ba61$3f078540$0d7ba8c0@ellacoya.com> <5332.1183135679@sss.pgh.pa.us> <4684F718.EE98.0025.0@wicourts.gov><4684F718.EE98.0025.0@wicourts.gov> <5750.1183138146@sss.pgh.pa.us> In-Reply-To: <5750.1183138146@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/309 X-Sequence-Number: 25977 >>> On Fri, Jun 29, 2007 at 12:29 PM, in message <5750.1183138146@sss.pgh.p= a.us>, Tom Lane wrote:=20 > "Kevin Grittner" writes: >> Tom Lane wrote: >>> Offhand I would recommend the same strategy for any requested filename >>> that's not a plain WAL segment file (ie, all hex digits). >>=20 >> I suspect that it's worth waiting for something like this, too?: >> 000000010000000A000000CF.0000E744.backup >=20 > No, I don't think so. AFAICS the slave server would only ask for one > of those during its initial cold start from a base backup, and it'll be > looking for the one that should have been generated at completion of > that base backup. If it ain't there, it's unlikely to appear later. Fair enough. It would have saved us some time if this was mentioned in the warm standby documentation. I'll try to put a doc patch together. =20 -Kevin =20