Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Date
Msg-id 603c8f071003250643k123070f9ufd1dbfca40481c4f@mail.gmail.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Thu, Mar 25, 2010 at 8:55 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> * 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.

I don't think we should be changing pre-9.0 behavior more than necessary.

...Robert


pgsql-hackers by date:

Previous
From: chaoyong wang
Date:
Subject: Access Violation when using Berkely DB in C-Language Function in VS2005
Next
From: Pei He
Date:
Subject: Ask help for putting SP-Gist into postgresql