Re: missing history file

>>> On Fri, Jun 29, 2007 at 12:29 PM, in message <5750(dot)1183138146(at)sss(dot)pgh(dot)pa(dot)us>,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Offhand I would recommend the same strategy for any requested filename
>>> that's not a plain WAL segment file (ie, all hex digits).
>>
>> I suspect that it's worth waiting for something like this, too?:
>> 000000010000000A000000CF.0000E744.backup
>
> 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.

-Kevin