From: Michael Stone <mstone+postgres@mathom.us>
To: pgsql-performance@postgresql.org
Subject: Re: SAN vs Internal Disks
Date: Fri, 07 Sep 2007 06:04:49 -0400
Message-ID: <20070907100446.GE1795@mathom.us> (raw)
In-Reply-To: <Pine.GSO.4.64.0709062354040.28915@westnet.com>
References: <a199704d0709060535q6fea139aq2e3863e685555b0d@mail.gmail.com>
<dcc563d10709060925o6f11f632sbfbc2b64530ae80d@mail.gmail.com>
<a199704d0709061003u71d536fbh9d71ed095dfe16b@mail.gmail.com>
<Pine.GSO.4.64.0709062354040.28915@westnet.com>
On Fri, Sep 07, 2007 at 12:26:23AM -0400, Greg Smith wrote:
>consider is this: your SAN starts having funky problems, and your
>database is down because of it. You call the vendor. They find out
>you're running CentOS instead of RHEL and say that's the cause of your
>problem (even though it probably isn't). How much will such a passing the
>buck problem cost your company? If it's a significant number, you'd be
>foolish to run CentOS instead of the real RHEL. Some SAN vendors can be
>very, very picky about what they will support, and for most business
>environments the RHEL subscription isn't so expensive that it's worth
>wandering into an area where your support situation is fuzzy just to save
>that money.
Correct. Far more sensible to skip the expensive SAN solution, not worry
about having to play games, and save *even more* money.
SANs have their place, but postgres storage generally isn't it; you'll
get more bang/buck with DAS and very likely better absolute performance
as well. SANs make sense if you're doing a shared filesystem (don't
even think about doing this with postgres), or if you're consolidating
backups & DR (which doesn't work especially well with databases).
Mike Stone
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: mstone+postgres@mathom.us
Subject: Re: SAN vs Internal Disks
In-Reply-To: <20070907100446.GE1795@mathom.us>
* 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