| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Jeff Davis <pgsql(at)j-davis(dot)com>, Yuri Levinsky <yuril(at)celltick(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Postgres crash? could not write to log file: No space left on device |
| Date: | 2013-06-26 14:15:25 |
| Message-ID: | 6022.1372256125@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dmcmillan | 2013-06-26 15:25:43 | BUG #8256: query screen on pgAdmin is show blank |
| Previous Message | Andres Freund | 2013-06-26 13:04:00 | Re: Postgres crash? could not write to log file: No space left on device |