Well our restore command is pretty basic:
restore_command = 'gunzip </wal_archive/%f.gz>%p'
I'm not sure why that would succeed then fail.
____________________________________________________________________
Brendan Duddridge | CTO | 403-277-5591 x24 | brendan@clickspace.com
ClickSpace Interactive Inc.
Suite L100, 239 - 10th Ave. SE
Calgary, AB T2G 0V9
http://www.clickspace.com
On Apr 20, 2006, at 5:20 PM, Tom Lane wrote:
> Brendan Duddridge <brendan@clickspace.com> writes:
>> However, as I just finished posting to the list, the process died
>> with a PANIC error:
>
>> [2006-04-20 16:41:28 MDT] LOG: restored log file
>> "000000010000018F00000034" from archive
>> [2006-04-20 16:41:35 MDT] LOG: restored log file
>> "000000010000018F00000035" from archive
>> [2006-04-20 16:41:38 MDT] LOG: restored log file
>> "000000010000018F00000036" from archive
>> sh: line 1: /wal_archive/000000010000018F00000037.gz: No such file or
>> directory
>> [2006-04-20 16:41:46 MDT] LOG: could not open file "pg_xlog/
>> 000000010000018F00000037" (log file 399, segment 55): No such file or
>> directory
>> [2006-04-20 16:41:46 MDT] LOG: redo done at 18F/36FFF254
>> sh: line 1: /wal_archive/000000010000018F00000036.gz: No such file or
>> directory
>> [2006-04-20 16:41:46 MDT] PANIC: could not open file "pg_xlog/
>> 000000010000018F00000036" (log file 399, segment 54): No such file or
>> directory
>
> This looks to me like a bug in your archive restore command. It had
> just finished providing 000000010000018F00000036 at 16:41:38, why was
> it not able to do so again at 16:41:46?
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that
> your
> message can get through to the mailing list cleanly
>