Re: Postgres crash? could not write to log file: No space left on device - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Postgres crash? could not write to log file: No space left on device
Date
Msg-id 6022.1372256125@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres crash? could not write to log file: No space left on device  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Postgres crash? could not write to log file: No space left on device
List pgsql-bugs
Heikki Linnakangas <hlinnakangas@vmware.com> writes:
> We've discussed retrying short writes before, and IIRC Tom has argued
> that it shouldn't be necessary when writing to disk. Nevertheless, I
> think we should retry in XLogWrite(). It can write much bigger chunks
> than most write() calls, so there's more room for a short write to
> happen there if it can happen at all. Secondly, it PANICs on failure, so
> it would be nice to try a bit harder to avoid that.

Seems reasonable.  My concern about the idea in general was the
impossibility of being sure we'd protected every single write() call.
But if we can identify specific call sites that seem at more risk than
most, I'm okay with adding extra logic there.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Yuri Levinsky"
Date:
Subject: Re: Postgres crash? could not write to log file: No spaceleft on device
Next
From: gabriel.ct@santamonicace.com.br
Date:
Subject: BUG #8255: encoding latin1