| From: | Chris Jones <chris(at)mt(dot)sri(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:54:15 |
| Message-ID: | 20010523115415.G437@mt.sri.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, May 23, 2001 at 01:47:37PM -0400, Tom Lane wrote:
> 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).
Yeah, my mistake.
> 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.
If write didn't return -1, it shouldn't have set errno. A short write
count isn't an error condition.
Chris
--
chris(at)mt(dot)sri(dot)com -----------------------------------------------------
Chris Jones SRI International, Inc.
www.sri.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hector Morales | 2001-05-23 17:56:42 | problema con buffer de psql |
| Previous Message | Tom Lane | 2001-05-23 17:47:37 | Re: Re: ZeroFill(.../pg_xlog/xlogtemp.20148) failed: No such file or directory |