From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200101020400.XAA06848@candle.pha.pa.us>
Subject: Re: Rather incorrect text in admin guide
In-Reply-To: <Pine.BSF.4.05.10012311025050.16414-100000@misery.sdf.com>
	"from Tom Samplonius at Dec 31, 2000 10:26:08 am"
To: Tom Samplonius <tom@sdf.com>
Date: Mon, 1 Jan 2001 23:00:55 -0500 (EST)
CC: Ralf Mattes <rm@mh-freiburg.de>, Michael Graff <explorer@flame.org>,
	pgsql-docs@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

I can only imagine how they got databases working through NFS.  Having
the backend on one server and the files on another is really quite risky.

> 
> On Sun, 31 Dec 2000, Ralf Mattes wrote:
> 
> > On Fri, Dec 29, 2000 at 07:05:41PM -0800, Tom Samplonius wrote:
> > >   Also NFSv2 is limited to 2GB, even if the client and server have no
> > > issues.  It is a protocol thing that is fixed in NFSv3.  I doubt that
> > > anyone is putting their postgres databases on a NFS server, but you never
> > > know.
> > 
> > It would be a bad idea to put the database on NFS but the paragraph
> > talks about possible problems during pg_dump and it doesn't seem
> > too unreasonable to dump a database to an NFS-mounted area.
> 
>   Well NetApp has gone through quite a bit of work getting their NFS
> filers Oracle and MS-SQL certified.  There are extensive tech notes on the
> Netapp site about Oracle and MS-SQL on NFS servers.
> 
> > Ralf Mattes
> > 
> > P.S: Happy new year :-)
> 
> 
> Tom
> 
> 


-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026