On Thu, Mar 25, 2010 at 9:55 PM, Heikki Linnakangas
> * 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.
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
Description: application/octet-stream (1.4 KB)
In response to
pgsql-docs by date
|Next:||From: Fujii Masao||Date: 2010-03-26 13:21:42|
|Subject: Re: [HACKERS] Incrementally Updated Backups and restartpoints|
|Previous:||From: Josh Kupershmidt||Date: 2010-03-26 03:43:13|
|Subject: docs cleanup patch|
pgsql-hackers by date
|Next:||From: Albe Laurenz||Date: 2010-03-26 08:03:57|
|Subject: Re: Ask help for putting SP-Gist into postgresql|
|Previous:||From: Joseph Adams||Date: 2010-03-26 03:42:48|
|Subject: Re: Proposal: access control jails (and introduction as aspiring GSoC student)|
pgsql-committers by date
|Next:||From: Heikki Linnakangas||Date: 2010-03-26 12:23:34|
|Subject: pgsql: Flush CopyOutResponse when starting streaming in walsender, so |
|Previous:||From: User Itagaki||Date: 2010-03-26 02:36:54|
|Subject: pgbulkload - pgbulkload: pg_bulkload 3.0 Alpha 3.|