Re: EINTR error in SunOS
- From: Rod Taylor <pg(at)rbt(dot)ca>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Greg Stark <gsstark(at)mit(dot)edu>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: EINTR error in SunOS
- Date: Sat, 31 Dec 2005 14:48:48 -0500
- Message-id: <1136058528.62046.10.camel@home> <text/plain>
On Sat, 2005-12-31 at 14:40 -0500, Tom Lane wrote:
> Greg Stark <gsstark(at)mit(dot)edu> writes:
> > Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)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?
--
Home |
Main Index |
Thread Index