pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dan The Man <bitsandbytes88@hotmail.com>
To: pgsql-admin@postgresql.org
To: daniel.kavan@medstar.net
Subject: 8.1.0 - PITR - cp:  cannot stat
Date: Tue, 06 Dec 2005 14:50:26 -0500
Message-ID: <BAY102-F191EF36E03532A31325E17D1400@phx.gbl> (raw)

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
##########################





Message-ID: <BAY102-F191EF36E03532A31325E17D1400@phx.gbl>
Permalink:  ../BAY102-F191EF36E03532A31325E17D1400@phx.gbl/
Also on:    postgresql.org/message-id/BAY102-F191EF36E03532A31325E17D1400@phx.gbl

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: bitsandbytes88@hotmail.com, daniel.kavan@medstar.net
  Subject: Re: 8.1.0 - PITR - cp:  cannot stat
  In-Reply-To: <BAY102-F191EF36E03532A31325E17D1400@phx.gbl>
  References: <BAY102-F191EF36E03532A31325E17D1400@phx.gbl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox