From: | "Shoaib Mir" <shoaibmir(at)gmail(dot)com> |
---|---|
To: | "PostgreSQL General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Recovery problem with PostgreSQL |
Date: | 2006-05-11 14:56:04 |
Message-ID: | bf54be870605110756vb733314x1b0acae0eba1cc63@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
That should be true about `/data1_node5/arch/00000001.history' since there
may not be any timelines created by previous archiver recoveries
But the message
cp: cannot stat `/data1_node5/arch/000000010000000000000007''
suggests that it was not able to restore one of the log files while doing
the recovery So it can be treated as an error I guess due to missing log
file in the archive folder. That might be due to the archive command not
setup correctly and as a result it was not able to copy files from pg_xlog
to archive folder.
/Shoaib
On 5/11/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Shoaib Mir" <shoaibmir(at)gmail(dot)com> writes:
> > While running the recovery process I am getting the following errors for
> > cannot stat:
>
> > cp: cannot stat `/data1_node5/arch/00000001.history': No such file or
> > directory
>
> What makes you think this is an error? As pointed out in the docs,
> the archive_recovery command *will* be asked for files that don't
> exist. You might want to tweak your script to not report an error
> in this case.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-11 14:56:20 | Re: [GENERAL] Debugging SQL queries |
Previous Message | Tony Caduto | 2006-05-11 14:39:59 | Re: [GENERAL] Debugging SQL queries |