| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Detecting corrupted pages earlier |
| Date: | 2003-02-20 02:01:24 |
| Message-ID: | 3E5436F4.429FD4C1@tpf.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > Tom Lane wrote:
> >> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> >>> Is there a way to make our way around the pages ?
> >>
> >> If the header is corrupt, I don't think so.
>
> > What I asked is how to read all other sane pages.
>
> Oh, I see. You can do "SELECT ... LIMIT n" to get the rows before the
> broken page, but there's no way to get the ones after it. My proposal
> won't make this worse, but it won't make it any better either. Do you
> have an idea how to get the rows after the broken page?
How about adding a new option to skip corrupted pages ?
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Clift | 2003-02-20 02:08:56 | Re: request for sql3 compliance for the update command |
| Previous Message | Tatsuo Ishii | 2003-02-20 01:17:01 | Re: request for sql3 compliance for the update command |