From: | Christof Petig <christof(dot)petig(at)wtal(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Recovery on incomplete write |
Date: | 1999-09-29 08:39:32 |
Message-ID: | 37F1D043.635CFC6C@wtal.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> >
> > 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.
It does corrupt the database (happened twice to me last week, I'm using the
current CVS version!). You can't even pg_dump the database - it stops in the
middle of a line.
And this happened just because some process went amok and stdout was written
to a file.
Christof
From | Date | Subject | |
---|---|---|---|
Next Message | Christof Petig | 1999-09-29 08:56:07 | Re: [PATCHES] ECPGlib: NULL into bool, force indicator on NULL (2 patches) |
Previous Message | Ansley, Michael | 1999-09-29 07:59:05 | RE: [HACKERS] MS Access upsizing |