Sorry for the delay. On Fri, Mar 19, 2010 at 8:37 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > Here's a patch I've been playing with.
Thanks! I'm reading the patch. > The idea is that in standby mode, > the server keeps trying to make progress in the recovery by: > > a) restoring files from archive > b) replaying files from pg_xlog > c) streaming from master > > When recovery reaches an invalid WAL record, typically caused by a > half-written WAL file, it closes the file and moves to the next source. > If an error is found in a file restored from archive or in a portion > just streamed from master, however, a PANIC is thrown, because it's not > expected to have errors in the archive or in the master. But in the current (v8.4 or before) behavior, recovery ends normally when an invalid record is found in an archived WAL file. Otherwise, the server would never be able to start normal processing when there is a corrupted archived file for some reasons. So, that invalid record should not be treated as a PANIC if the server is not in standby mode or the trigger file has been created. Thought? When I tested the patch, the following PANIC error was thrown in the normal archive recovery. This seems to derive from the above change. The detail error sequence: 1. In ReadRecord(), emode was set to PANIC after 00000001000000000000000B was read. 2. 00000001000000000000000C including the contrecord tried to be read by using the emode (= PANIC). But since 00000001000000000000000C did not exist, PANIC error was thrown. ----------------- LOG: restored log file "00000001000000000000000B" from archive cp: cannot stat `../data.arh/00000001000000000000000C': No such file or directory PANIC: could not open file "pg_xlog/00000001000000000000000C" (log file 0, segment 12): No such file or directory LOG: startup process (PID 17204) was terminated by signal 6: Aborted LOG: terminating any other active server processes ----------------- Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
