<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for the prompt response. If such a file is needed for recovery
it was never created by postgres. The current archiving process creates
uses rsync to archive the WAL files to a shared archive area. In the
past and on my other cluster we do not see .history files on the
primary server and have been able to recover without them. If it helps
I can send a copy of the WAL files and my postgres.conf files. <br>
<br>
Keith<br>
<br>
Tom Lane wrote:
<blockquote cite="mid:21020(dot)1245090610(at)sss(dot)pgh(dot)pa(dot)us" type="cite">
<pre wrap="">"Keith Pierno" <a class="moz-txt-link-rfc2396E" href="mailto:kpierno(at)lulu(dot)com"><kpierno(at)lulu(dot)com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">2009-06-15 13:25:12 EDT <::> PANIC: unexpected timeline ID 6 (after 4) in
checkpoint record
</pre>
</blockquote>
<pre wrap=""><!---->
Hmm. It's complaining because it didn't find timeline 6 mentioned in
the timeline history file it read (if any). Maybe you forgot to archive
or restore the NNNNNNNN.history file?
regards, tom lane
</pre>
</blockquote>
<br>
</body>
</html>