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

Re: PostgreSQL NetApp and NFS

From: Jurgen Haan <jurgen(at)easyflex(dot)nl>
Cc: PGSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: PostgreSQL NetApp and NFS
Date: 2008-03-25 13:33:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Well, we're not running PGSQL on a Netapp over NFS, but a DB2 Database.
But nevertheless, it runs quite well. NFS is not a bad choice for your
database, the big memory buffer that allocates the raid6 blocks makes it
all very quick, like you're working directly on a 1+ TB ramdisk.

One important thing to keep in mind, is to make sure the NFS protocol
used is at least V3 and to check your locking options.
This made our DB2 crash, because when configured wrong, the file locking
mechanism on an NFS mount behaves differently than that of the local
storage. These parameters can be forced from the client side (fstab).

But still, with our 100+ GB OLTP database, I'm still quite fond of our


Chris Hoover wrote:
> I just found out that my company is planning on migrating my databases
> from our current ISCSI storage solution to NetApps connected via NFS.  I
> knew about the NetApp migration, but always assumed (and shame on me)
> that I would have direct attachments to the servers.

> Chris
> -- 
> Come see how to SAVE money on fuel, decrease harmful emissions, and even
> make MONEY. Visit and join the revolution!

Easyflex diensten b.v.
Acaciastraat 16
4921 MA  MADE
T: 0162 - 690410
F: 0162 - 690419
E: info(at)easyflex(dot)nl

In response to

pgsql-performance by date

Next:From: Bill MoranDate: 2008-03-25 13:34:40
Subject: Re: what is the maximum number of rows in a table in postgresql 8.1
Previous:From: sathiya psqlDate: 2008-03-25 13:27:12
Subject: Re: postgresql is slow with larger table even it is in RAM

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