DATA directory on network attached storage

From: Jeff Frost <jeff(at)frostconsultingllc(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: sfpug(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org
Subject: DATA directory on network attached storage
Date: 2005-04-08 17:01:55
Message-ID: Pine.LNX.4.62.0504080957220.11558@discord.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance sfpug

We are currently considering the possibility of creating a warm standby
machine utilizing heartbeat and a network attached storage device for the DATA
directory. The idea being that the warm standby machine has its postmaster
stopped. When heartbeat detects the death of the master server, the
postmaster is started up on the warm standby using the shared DATA directory.
Other than the obvious problems of both postmasters inadvertently attempting
access at the same time, I'm curious to know if anyone has tried any similar
setups and what the experiences have been. Specifically is the performance of
gigE good enough to allow postgres to perform under load with an NFS mounted
DATA dir? Are there other problems I haven't thought about? Any input would
be greatly appreciated.

Thanks!

--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2005-04-08 17:05:45 Re: [sfpug] DATA directory on network attached storage
Previous Message Qingqing Zhou 2005-04-08 05:36:40 Re: Compressing WAL

Browse sfpug by date

  From Date Subject
Next Message Josh Berkus 2005-04-08 17:03:04 Soliciting for future topic requests
Previous Message Josh Berkus 2005-04-08 16:57:27 Meeting on Tuesday, Time, Topic