From: Tobias Brox <tobias@nordicbet.com>
To: pgsql-performance@postgresql.org
Subject: Re: SAN vs Internal Disks
Date: Fri, 7 Sep 2007 12:33:41 +0200
Message-ID: <20070907103341.GC20896@oppetid.no> (raw)
In-Reply-To: <20070907100446.GE1795@mathom.us>
References: <a199704d0709060535q6fea139aq2e3863e685555b0d@mail.gmail.com>
<dcc563d10709060925o6f11f632sbfbc2b64530ae80d@mail.gmail.com>
<a199704d0709061003u71d536fbh9d71ed095dfe16b@mail.gmail.com>
<Pine.GSO.4.64.0709062354040.28915@westnet.com>
<20070907100446.GE1795@mathom.us>
We're also considering to install postgres on SAN - that is, my boss is
convinced this is the right way to go.
Advantages:
1. Higher I/O (at least the salesman claims so)
2. Easier to upgrade the disk capacity
3. Easy to set up "warm standby" functionality. (Then again, if the
postgres server fails miserably, it's likely to be due to a disk
crash).
Also, my boss states that "all big enterprises uses SAN nowadays".
Disadvantages:
1. Risky? One gets the impression that there are frequent problems
with data integrity when reading some of the posts in this thread.
2. Expensive
3. "Single point of failure" ... but that you have either it's a SAN or
a local disk, one will anyway need good backup systems (and eventually
"warm standby"-servers running from physically separated disks).
4. More complex setup?
5. If there are several hosts with write permission towards the same
disk, I can imagine the risks being higher for data integrity
breakages. Particularly, I can imagine that if two postgres instances
is started up towards the same disk (due to some sysadmin mistake), it
could be disasterous.
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: tobias@nordicbet.com
Subject: Re: SAN vs Internal Disks
In-Reply-To: <20070907103341.GC20896@oppetid.no>
* 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