From: Joe Conway <mail@joeconway.com>
To: Aditya <aditya@grot.org>
Cc: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: sfpug@postgresql.org
Cc: pgsql-performance@postgresql.org
Subject: Re: [sfpug] DATA directory on network attached storage
Date: Mon, 11 Apr 2005 10:59:51 -0700
Message-ID: <425ABB17.305@joeconway.com> (raw)
In-Reply-To: <20050408192136.GD72199@mighty.grot.org>
References: <200502091350.24885.josh@agliodbs.com>
<Pine.LNX.4.62.0504080957220.11558@discord.dyndns.org>
<20050408192136.GD72199@mighty.grot.org>
Aditya wrote:
> We have not, AFAICT, had any problems with the traffic over NFS as far as
> reliability -- I'm sure there is a performance penalty, but the reliability
> and scalability gains more than offset that.
My experience agrees with yours. However we did find one gotcha -- see
the thread starting here for details:
http://archives.postgresql.org/pgsql-hackers/2004-12/msg00479.php
In a nutshell, be careful when using an nfs mounted data directory
combined with an init script that creates a new data dir when it doesn't
find one.
> FWIW, if I were to do this anew, I would probably opt for iSCSI over GigE with
> a NetApp.
Any particular reason? Our NetApp technical rep advised nfs over iSCSI,
IIRC because of performance.
Joe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mail@joeconway.com, aditya@grot.org, jeff@frostconsultingllc.com, josh@agliodbs.com, sfpug@postgresql.org
Subject: Re: [sfpug] DATA directory on network attached storage
In-Reply-To: <425ABB17.305@joeconway.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox