From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Vadim Mikheev <vmikheev(at)sectorbase(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Theory about XLogFlush startup failures |
Date: | 2002-01-16 00:19:11 |
Message-ID: | 3C44C6FF.9AE5742@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2002-01-16 00:58:21 | Re: 7.1 vs. 7.2 on AIX 5L |
Previous Message | Tom Lane | 2002-01-15 23:46:48 | tuptoaster.c must *not* use SnapshotAny |