Robert Haas wrote: > On Fri, Jan 29, 2010 at 11:02 AM, Fujii Masao <masao.fu...@gmail.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. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
