Skip site navigation (1) Skip section navigation (2)

Re: WAL recovery failure

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Rick Dicaire *EXTERN*" <kritek(at)gmail(dot)com>,"Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: WAL recovery failure
Date: 2012-09-26 09:21:08
Message-ID: D960CB61B694CF459DCFB4B0128514C20874BE8A@exadv11.host.magwien.gv.at (view raw or flat)
Thread:
Lists: pgsql-admin
Rick Dicaire wrote:
>> /staging/9.1/main/pg_xlog is really archive directory?
restore_command
>> should be set to the command which copies the archived WAL files from
>> the archive area.
> 
> Yes. This is the archive directory.

But according to what you wrote before you start the server
with -D /staging/9.1/main.
That means that /staging/9.1/main/pg_xlog contains the active
WAL files, right?

So the restore_command 'cp /staging/9.1/main/pg_xlog/%f "%p"'
would just try to cp the files onto themselves, right?

The WAL archive directory must be different from the
active WAL directory.  Check if that's your problem!

Yours,
Laurenz Albe


In response to

Responses

pgsql-admin by date

Next:From: Rick DicaireDate: 2012-09-26 11:35:13
Subject: Re: WAL recovery failure
Previous:From: Rick DicaireDate: 2012-09-26 01:56:21
Subject: Re: WAL recovery failure

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group