On Thu, Mar 25, 2010 at 9:55 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > * Fix the bug of a spurious PANIC in archive recovery, if the WAL ends > in the middle of a WAL record that continues over a WAL segment boundary. > > * If a corrupt WAL record is found in archive or streamed from master in > standby mode, throw WARNING instead of PANIC, and keep trying. In > archive recovery (ie. standby_mode=off) it's still a PANIC. We can make > it a WARNING too, which gives the pre-9.0 behavior of starting up the > server on corruption. I prefer PANIC but the discussion is still going on.
Seems reasonable for me. > * Small code changes to handling of failedSources, inspired by your > comment. No change in functionality. > > This is also available in my git repository at > git://git.postgresql.org/git/users/heikki/postgres.git, branch "xlogchanges" I looked the patch and was not able to find any big problems until now. The attached small patch fixes the typo. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
typo.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
