Skip site navigation (1) Skip section navigation (2)

Re: Rather incorrect text in admin guide

From: Tom Samplonius <tom(at)sdf(dot)com>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Ralf Mattes <rm(at)mh-freiburg(dot)de>, Michael Graff <explorer(at)flame(dot)org>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Rather incorrect text in admin guide
Date: 2001-01-03 01:38:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
On Tue, 2 Jan 2001, The Hermit Hacker wrote:

> > > > 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.
> > >
> > >   Well, both Microsoft and Oracle support NFS mounted database device
> > > files with NetApp filers.
> >
> > Quite a trick.  NFS, being state-less, is really a bad platform for such
> > things.  I know there is NFS locking, but even that is not 100%, if I
> > remember correctly.
> NFS is state-less if you use UDP connections ... most modern Unices
> support TCP NFS as well, providing you a stateful connection ...

  A stateless procotol riding on a stateful protocol, is still stateless.
Think HTTP.

  The fact that NFS is stateless or not, does not matter for database
application.  In the supported configuration, only one server is allowed
to mount the database at one time anyway.  The only issue is making sure
that NFS writes actually get written when the NFS servers says they have
been written to ensure database consistancy.  Many NFS implementations ack
NFS writes before they are written NetApp uses a battery backed RAM as a
write cache.


In response to

pgsql-docs by date

Next:From: Lincoln YeohDate: 2001-01-03 02:37:31
Subject: Re: RE: Re: MySQL and PostgreSQL speed compare
Previous:From: Vince VielhaberDate: 2001-01-03 01:12:17
Subject: Re: RE: Re: MySQL and PostgreSQL speed compare

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group