My experience postgresql work good on NFS. Of course, use NFS over TCP, and
use noac if you want to protect your database even more (my experience is
NFS client caching doesn't lead to an irrecoverable database however)
I've encountered problems with RHEL4 as a database server and a client of a
Netapp filer, due to a bug in the (redhat nfs client)
Postgresql uses BSD read/write semantics. The BSD semantics mean an IO call
(either read or write) is atomic.
Linux uses system V read/write semantics. The system V semantics mean an IO
is NOT atomic and can be interrupted.
A read call got interrupted (due to the bug in the nfs client), which meant
the IO call kept waiting until infinity.
It even caused all other IO done against the inode to be waiting, leading to
a situation where the server needed a reboot to be able to function
On Thu, Mar 20, 2008 at 9:09 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Chris Hoover wrote:
> > If you have any real life good or bad stories, I'd love to hear it.
> > the NetApp arrays supposedly being very good NFS platforms, overall, is
> > a recommended way to run PostgreSQL, or is it recommended to not run
> > way.
> We do have an NFS section in our documentation at the bottom of this
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://postgres.enterprisedb.com
> + If your life is a hard drive, Christ can be your backup. +
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2008-03-20 21:52:29|
|Subject: Re: PostgreSQL NetApp and NFS |
|Previous:||From: Woody Woodring||Date: 2008-03-20 20:45:14|
|Subject: Re: PostgreSQL NetApp and NFS|