Re: Re: ZeroFill(.../pg_xlog/xlogtemp.20148) failed: No such file or directory
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris Jones <chris@mt.sri.com>
Cc: Oliver Elphick <olly@lfix.co.uk>, pgsql-general@postgresql.org
Date: 2001-05-23T17:47:37Z
Lists: pgsql-general
Chris Jones <chris@mt.sri.com> writes: > No, it could be any number of other things. The first that comes to > mind is EINTR. How about something closer to: Writes to disk files don't suffer EINTR as far as I've ever heard (if they do, there are an awful lot of broken programs out there). More to the point, a kernel that aborted a write because of an interrupt *and failed to set errno* would certainly be broken. The question is what to assume when we see that the write did not change errno. regards, tom lane