Re: EINTR error in SunOS - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: EINTR error in SunOS
Date
Msg-id 1136058528.62046.10.camel@home
Whole thread Raw
In response to Re: EINTR error in SunOS  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: EINTR error in SunOS  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
On Sat, 2005-12-31 at 14:40 -0500, Tom Lane wrote:
> Greg Stark <gsstark@mit.edu> writes:
> > Qingqing Zhou <zhouqq@cs.toronto.edu> writes:
> >> I have patched IO routines in backend/storage that POSIX says EINTR is
> >> possible except unlink(). Though POSIX says EINTR is not possible, during
> >> many regressions, I found it sometimes sets this errno on NFS (I still
> >> don't know where is the smoking-gun):
> 
> > Well there is a reason intr is not the default for NFS mounts. It's precisely
> > because it breaks the traditional unix filesystem interface.

> What I'd rather do is document prominently that running a DB over NFS
> isn't recommended, and running it over NFS with interrupts allowed is
> just not going to work.

Are there issues with having an archive_command which does things with
NFS based filesystems?

-- 



pgsql-hackers by date:

Previous
From: Qingqing Zhou
Date:
Subject: Re: EINTR error in SunOS
Next
From: Tom Lane
Date:
Subject: Re: Removing SORTFUNC_LT/REVLT