Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id A32481337B92
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed,  9 Feb 2011 15:31:39 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 20583-06 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed,  9 Feb 2011 19:31:32 +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 6270B1337B83
	for <pgsql-admin@postgresql.org>; Wed,  9 Feb 2011 15:31:32 -0400 (AST)
Received: by vws16 with SMTP id 16so330624vws.19
	for <pgsql-admin@postgresql.org>; Wed, 09 Feb 2011 11:31:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:from:content-type:content-transfer-encoding
	:subject:date:message-id:to:mime-version:x-mailer;
	bh=QTpt9W5mCDo3NZMVq0RAK3qIemGv48HUU0Z4IDce+H8=;
	b=NSUwVfOhCAefYo0UNELinEbiZmgQuotYmxwwdmYytTrqnJ9puQN97MJP3WzLnR550q
	cIdt8cZmEYqDuiBRQcdfD6eoqqZxLoVoF7qZ7LIfi9T6dKslKXt6hAN/PLUqn0fiLDyM
	16+Bws4vAn6m0+0RURJEGwdENVdOl0tfdTOu4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=from:content-type:content-transfer-encoding:subject:date:message-id
	:to:mime-version:x-mailer;
	b=SCGlvj6d8hq8JojaNZBn5V5PUChvZhjIU6wbjGpNa6vQ8Z00ZDRYsqQqdZA3OE18lt
	v91Pq7ClROlFcGcjXanouGY1g+iDDncKUUKskOV6+xynyhpVit9J5XX70gQKecBMvCIT
	TvFSq+KCcBTU53wqSk9IakIxvpCCDMWEbYLXo=
Received: by 10.220.182.196 with SMTP id cd4mr5204509vcb.177.1297279891956;
	Wed, 09 Feb 2011 11:31:31 -0800 (PST)
Received: from [10.41.41.88] ([216.55.28.254])
	by mx.google.com with ESMTPS id b6sm223011vci.24.2011.02.09.11.31.30
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 09 Feb 2011 11:31:31 -0800 (PST)
From: Bryan Keller <bryanck@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Postgres on NAS/NFS
Date: Wed, 9 Feb 2011 11:31:29 -0800
Message-Id: <77A74B6C-A4BE-4659-A07A-2F03B617DF7B@gmail.com>
To: pgsql-admin@postgresql.org
Mime-Version: 1.0 (Apple Message framework v1082)
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/80
X-Sequence-Number: 36719

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 cause data corruption.

My goal is to have the database on a shared filesystem so in case of =
server failure, I can start up a standby Postgres server and point it to =
the same database. I would rather not use a SAN as I have heard horror =
stories about managing them. Also they are extremely expensive. A DAS =
would be another option, but I'm not sure if a DAS can be connected to =
two servers for server failover purposes.

Currently I am considering not using a shared filesystem and instead =
using replication between the two servers.

I am wondering what solutions have others used for my active-passive =
Postgres failover scenario? Is a NAS still not a recommended approach? =
Will a DAS work?