Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 08D8C1337B98 for ; Mon, 14 Feb 2011 14:06:33 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 12601-09 for ; Mon, 14 Feb 2011 18:06:25 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by mail.postgresql.org (Postfix) with ESMTP id 4B3181337B34 for ; Mon, 14 Feb 2011 14:06:25 -0400 (AST) Received: by vws16 with SMTP id 16so3216488vws.19 for ; Mon, 14 Feb 2011 10:06:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=4l6ihI64+0Yo3Pr1DEslcNHoOFW3pC5NITfPIpNO1xE=; b=Di5joyI773av5CevK3waO8V2xwppKOMnBf289/sZA2etp4OQTEpb7h0tgGokAvSoB7 lXUiaJjfkcbFYu35IMjS7MdIQYdqmNkcbP/IJb1zHCSVLuJ1MEKxDC7dZHua32WUfgAM mmdqs8dvrgssbS70kl9ALZEE2C6BHoaAdy0o4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=V2tMeCiLF56ZTn/0mJUuwARvJsEZfwhlfMtkC50eHyyyGh//b8uvCaZB+d5XaE+gGy qcAwxdlHGUG8lMfnNixfrkW1PAM2P2YO2nHq6NbGIaSy7pwDNWIx3Q4kNWgPtwLeZEOG BoiPdwqeVMgEtjEoJG3S7wlp7hzRaaxeVvKg4= Received: by 10.220.179.65 with SMTP id bp1mr1374123vcb.41.1297706754689; Mon, 14 Feb 2011 10:05:54 -0800 (PST) Received: from [10.41.41.88] ([216.55.28.254]) by mx.google.com with ESMTPS id q5sm807010vcr.39.2011.02.14.10.05.45 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Feb 2011 10:05:46 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) Subject: Re: Postgres on NAS/NFS From: Bryan Keller In-Reply-To: Date: Mon, 14 Feb 2011 10:05:43 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9424C7B4-672D-4C64-BE6A-699708981C0B@gmail.com> To: pgsql-admin@postgresql.org X-Mailer: Apple Mail (2.1082) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.589 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201102/117 X-Sequence-Number: 36756 Thanks for the feedback. It sounds like NFS is a viable solution = nowadays. I a still going to shoot for using iSCSI, given it is a = block-level protocol rather than file-level, it seems to me it would be = better suited to database I/O. On Feb 14, 2011, at 2:07 AM, Stuart Bishop wrote: > On Thu, Feb 10, 2011 at 2:59 AM, Bryan Keller = wrote: >=20 >> I am considering running a Postgres with the database hosted on a NAS = via NFS. I have read a few things on the Web saying this is not = recommended, as it will be slow and could potentially cause data = corruption. >=20 > Its not recommended if you have a crap NFS implementation. I think it > was about 10 years ago I ran Oracle under Solaris with a Netapp for > storage. Rock solid, supported configuration, and actually > outperformed using local disk. Hopefully the open source NFS clients > have caught up by now - if you see problem reports or recommendations, > pay attention to the platform and implementation rather than the > protocol. >=20 >=20 > --=20 > Stuart Bishop > http://www.stuartbishop.net/