Re: Re: ZeroFill(.../pg_xlog/xlogtemp.20148) failed: No such file or directory

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Jones <chris(at)mt(dot)sri(dot)com>
Cc: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org
Subject: Re: Re: ZeroFill(.../pg_xlog/xlogtemp.20148) failed: No such file or directory
Date: 2001-05-23 17:47:37
Message-ID: 16006.990640057@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Chris Jones <chris(at)mt(dot)sri(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Jones 2001-05-23 17:54:15 Re: Re: ZeroFill(.../pg_xlog/xlogtemp.20148) failed: No such file or directory
Previous Message Chris Jones 2001-05-23 17:44:51 Re: Re: ZeroFill(.../pg_xlog/xlogtemp.20148) failed: No such file or directory