Re: Postgres on NAS/NFS - Mailing list pgsql-admin

From Jim Mlodgenski
Subject Re: Postgres on NAS/NFS
Date
Msg-id AANLkTi=vkCQfQhQdp_cghbwrJaYYUVSt6E1_mLkEARn9@mail.gmail.com
Whole thread Raw
In response to Postgres on NAS/NFS  (Bryan Keller <bryanck@gmail.com>)
Responses Re: Postgres on NAS/NFS  (CS DBA <cs_dba@consistentstate.com>)
List pgsql-admin
On Wed, Feb 9, 2011 at 2:59 PM, Bryan Keller <bryanck@gmail.com> wrote:
> I am considering running a Postgres with the database hosted on a NAS via NFS. I have read a few things on the Web
sayingthis is not recommended, as it will be slow and could potentially 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
Postgresserver and point it to the same database. I would rather not use a SAN as I have heard horror stories about
managingthem. Also they are extremely expensive. A DAS would be another option, but I'm not sure if a DAS can be
connectedto 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
recommendedapproach? Will a DAS work? Or is replication the best approach? 

DAS will absolutely work. Just be careful to fence things properly so
that you don't end up with 2 servers trying to start the data
directory at the same time. It will lead to some pretty nasty
corruption.

>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

pgsql-admin by date:

Previous
From: "Nicholson, Brad (Toronto, ON, CA)"
Date:
Subject: Determining the WAL file needed by a standby
Next
From: Jaime Casanova
Date:
Subject: Re: Determining the WAL file needed by a standby