Date: Wed, 24 Mar 2010 16:54:44 -0400
From: Ray Stell <stellr@cns.vt.edu>
To: pgsql-admin@postgresql.org
Subject: Re: 8.2.15 pitr/00000001.history
Message-ID: <20100324205444.GB21072@cns.vt.edu>
References: <20100324171031.GA13674@cns.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100324171031.GA13674@cns.vt.edu>
User-Agent: Mutt/1.5.17 (2007-11-01)

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.