Hi,
I found this old post - see the bottom of the message. I'm having a
similiar issue. After a PITR everything looks good. I do see the following
in the logs: Can that be safely ignored?
cp cannot stat `/sprj/sqldumps_Linux.pgsql_carp5442/00000002.history': No
such file or directory
cp: cannot stat
`/sprj/sqldumps_Linux.pgsql_carp5442/000000020000001600000054': No such file
or directory
~DjK
###############
Those files do show up in my PGDATA directory just fine.
000001600000063 00000001000000160000007B
000000010000001600000064 00000001000000160000007C
000000010000001600000065 00000001000000160000007D
000000010000001600000066 000000020000001600000054
000000010000001600000067 000000020000001600000055
000000010000001600000068 00000002.history
000000010000001600000069 archive_status
postgres@tarpon:/sqldata/Linux.pgsql/tarpon5442/pg_xlog>
postgres@tarpon:/sqldata/Linux.pgsql/tarpon5442/pg_xlog>
################
I found the following old post but I didn't see anything in the 8.1 pdf on
nonexistent files.
:
Tom Lane wrote:
Gaetano Mendola <mendola ( at ) bigfoot ( dot ) com> writes:
I did a recovery strictly following the doc instructions, the recovery
succeded but I'm wondering if the following line in the logs is normal
or not.
cp: cannot stat `/home/pitr/00000001.history': No such file or
directory
Yes, see the point in the docs that the recovery_command *will* be asked
for nonexistent files.
Thanks, I got it.
Regards
Gaetano Mendola
##########################
