From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Crash during WAL recovery? |
Date: | 2000-11-21 22:01:07 |
Message-ID: | 8F4C99C66D04D4118F580090272A7A234D31A7@sectorbase1.sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-11-21 22:03:42 | Crash during WAL recovery? |
Previous Message | Peter Eisentraut | 2000-11-21 18:35:21 | Re: Questions on RI spec (poss. bugs) |