From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Larry Rosenman <ler(at)lerctr(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, michael(at)synchronicity(dot)com, Pgsql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_ctl reload - is it safe? |
Date: | 2003-10-14 19:38:32 |
Message-ID: | 200310141938.h9EJcWG23773@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Larry Rosenman wrote:
-- Start of PGP signed section.
>
>
> --On Tuesday, October 14, 2003 15:31:42 -0400 Bruce Momjian
> <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
>
> > Tom Lane wrote:
> >> Michael Brusser <michael(at)synchronicity(dot)com> writes:
> >> > Yes, we use NFS. Many of our customers use it as well.
> >>
> >> You are of course aware that this is not real safe...
> >
> > Maybe we should throw a "stop using NFS" if we get an EINTR from
> > read()/write(), or explain what NFS options they should avoid.
> Err, some of us use NetApp filers as NFS servers for our PG data, and I
> believe that that negates at least some of the risk. I don't want to see
> us (PG) not support something just because it *MAY* be unsafe.
True. I was going by the guy who said that only unsafe NFS flags will
cause this behavior --- and of course, 1/2 of it was a joke, and the
other 1/2 was just an idea thrown out.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | scott.marlowe | 2003-10-14 19:39:17 | Re: pg_ctl reload - is it safe? |
Previous Message | Bruce Momjian | 2003-10-14 19:37:28 | Re: fix for strict-alias warnings |