Robert Haas wrote:
> On Fri, Jan 29, 2010 at 11:02 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> You seem to focus on the above trouble. I think that this happened because
>> recovery.conf was deleted and restore_command was not given. In fact, the
>> WAL file (e.g., pg_xlog/0000000200003C82000000A3) required for recovery
>> was unable to be restored from the archive because restore_command was
>> not supplied. Then recovery failed.
>> If the sysadmin had left the recovery.conf and removed the trigger file,
>> pg_standby in restore_command would have restored all WAL files required
>> for recovery, and recovery would advance well.
> That may be true, but it's certainly seems unfortunate that we don't
> handle this case a bit more gracefully.
Yeah. I don't think we can do much better in versions <= 8.3, though we
should change that unlink() call to cause the FATAL error in a more
explicit way; it seems accidental and possibly non-portable as it is.
Adding the note to the docs that Mason suggested is a good idea.
In response to
pgsql-bugs by date
|Next:||From: Kevin Grittner||Date: 2010-01-29 19:15:53|
|Subject: Re: BUG #5299: unable to start postgres service|
|Previous:||From: Florian Nigsch||Date: 2010-01-29 19:07:37|
|Subject: BUG #5302: WIN1252 encoding causes server memory leak|