RE: Crash during WAL recovery? - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: Crash during WAL recovery?
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D31A7@sectorbase1.sectorbase.com
Whole thread Raw
In response to Crash during WAL recovery?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
> This snippet in xlog.c makes we wonder...
> 
>     else if (ControlFile->state == DB_IN_RECOVERY)
>     {
>         elog(LOG, "Data Base System was interrupted 
> being in recovery at %s\n"
>              "\tThis propably means that some data 
> blocks are corrupted\n"
>              "\tAnd you will have to use last 
> backup for recovery",
>              str_time(ControlFile->time));
>     }
> 
> I thought this was going to be crash safe.

WAL doesn't protect against disk block corruption what
could be reason of crash (or elog(STOP)) during recovery
in most cases. Apart from disk corruption recovery is
(or should be -:)) crash safe.

Vadim


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Crash during WAL recovery?
Next
From: Don Baccus
Date:
Subject: RE: Crash during WAL recovery?