Re: Theory about XLogFlush startup failures - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject Re: Theory about XLogFlush startup failures
Date
Msg-id 3C44C6FF.9AE5742@tpf.co.jp
Whole thread Raw
In response to Re: Theory about XLogFlush startup failures  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
List pgsql-hackers
Tom Lane wrote:
> 
> "Hiroshi Inoue" <Inoue@tpf.co.jp> writes:
> > What I have minded is e.g. the following case.
> > Undoubtedly the page is corrupted(too big offset number).
> > I'm suspicious if other pages are safe under such a situation.
> 
> You have a point, but I still don't like slowing down PageGetItem.
> 
> How about this instead: whenever we read in a page, check to see
> if its page header data is sane.  We could do this right after the
> smgrread call in ReadBufferInternal, and follow the "status = SM_FAIL"
> exit path if we see trouble.

Agreed. What we really expect is to not see such troubles
from the first.

regards,
Hiroshi Inoue


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: tuptoaster.c must *not* use SnapshotAny
Next
From: Tatsuo Ishii
Date:
Subject: Re: 7.1 vs. 7.2 on AIX 5L