RE: [HACKERS] Recovery on incomplete write

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Bruce Momjian" <maillist(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: [HACKERS] Recovery on incomplete write
Date: 1999-09-29 07:20:14
Message-ID: 001001bf0a4b$12b46360$2801007e@cadzone.tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> -----Original Message-----
> From: Bruce Momjian [mailto:maillist(at)candle(dot)pha(dot)pa(dot)us]
> Sent: Tuesday, September 28, 1999 11:54 PM
> To: Tom Lane
> Cc: Hiroshi Inoue; pgsql-hackers
> Subject: Re: [HACKERS] Recovery on incomplete write
>
>
> > "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> > > I have wondered that md.c handles incomplete block(page)s
> > > correctly.
> > > Am I mistaken ?
> >
> > I think you are right, and there may be some other trouble spots in that
> > file too. I remember thinking that the code depended heavily on never
> > having a partial block at the end of the file.
> >
> > But is it worth fixing? The only way I can see for the file length
> > to become funny is if we run out of disk space part way through writing
> > a page, which seems unlikely...
> >
>
> That is how he got started, the TODO item about running out of disk
> space causing corrupted databases. I think it needs a fix, if we can.
>

Maybe it isn't so difficult to fix.
I would provide a patch.

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ansley, Michael 1999-09-29 07:59:05 RE: [HACKERS] MS Access upsizing
Previous Message Mike Mascari 1999-09-29 05:45:51 Re: [HACKERS] DROP TABLE inside transaction block