From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201003242144.o2OLiKT01653@momjian.us>
Subject: Re: 8.2.15 pitr/00000001.history
In-Reply-To: <20100324205444.GB21072@cns.vt.edu>
To: Ray Stell <stellr@cns.vt.edu>
Date: Wed, 24 Mar 2010 17:44:20 -0400 (EDT)
CC: pgsql-admin@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Ray Stell wrote:
> On Wed, Mar 24, 2010 at 01:10:31PM -0400, Ray Stell wrote:
> >  2010-03-24 12:38:36.357 EDT,,3,,, LOG:  restore_command = "cp /home/postgresql/fms/wals/%f %p"
> >    cp: cannot stat `/home/postgresql/fms/wals/00000001.history': No such file or directory
> 
> patience, young padawan:
> 
> 2010-03-24 12:38:47.028 EDT,,31,,, LOG:  restored log file "0000000100000028000000EA" from archive
> cp: cannot stat `/home/postgresql/fms/wals/00000002.history': No such file or directory
> 2010-03-24 12:38:47.032 EDT,,32,,, LOG:  selected new timeline ID: 2
> cp: cannot stat `/home/postgresql/fms/wals/00000001.history': No such file or directory
> 2010-03-24 12:38:47.876 EDT,,33,,, LOG:  archive recovery complete
> 2010-03-24 12:38:49.478 EDT,,34,,, LOG:  database system is ready
> 2010-03-24 12:38:49.520 EDT,,1,,, LOG:  archived transaction log file "00000002.history"
> 
> src/backend/access/transam/xlog.c
>         /*
>          * Consider whether we need to assign a new timeline ID.
>          *
>          * If we are doing an archive recovery, we always assign a new ID. 

There is also change in 9.0:

	Fix longstanding gripe that we check for 0000000001.history at start of
	archive recovery, even when we know it is never present.

so you should not see this when using >= PG 9.0.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  PG East:  http://www.enterprisedb.com/community/nav-pg-east-2010.do