From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: pgsql-performance@postgresql.org
Subject: Re: Hardware/OS recommendations for large databases (
Date: Wed, 16 Nov 2005 19:51:38 +0100
Message-ID: <20051116185138.GA22831@uio.no> (raw)
In-Reply-To: <1132160785.3582.60.camel@state.g2switchworks.com>
References: <3E37B936B592014B978C4415F90D662D01995F7B@MI8NYCMAIL06.Mi8.com>
<33c6269f0511152115v1a34ab81j30f1f5df5a6c6956@mail.gmail.com>
<437B3B18.1040509@commandprompt.com>
<437B4773.1040404@boreham.org>
<1132160785.3582.60.camel@state.g2switchworks.com>
On Wed, Nov 16, 2005 at 11:06:25AM -0600, Scott Marlowe wrote:
> There was a big commercial EMC style array in the hosting center at the
> same place that had something like a 16 wide by 16 tall array of IDE
> drives for storing pdf / tiff stuff on it, and we had at least one
> failure a month in it. Of course, that's 256 drives, so you're gonna
> have failures, and it was configured with a spare on every other row or
> some such. We just had a big box of hard drives and it was smart enough
> to rebuild automagically when you put a new one in, so the maintenance
> wasn't really that bad. The performance was quite impressive too.
If you have a cool SAN, it alerts you and removes all data off a disk
_before_ it starts giving hard failures :-)
/* Steinar */
--
Homepage: http://www.sesse.net/
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: sgunderson@bigfoot.com
Subject: Re: Hardware/OS recommendations for large databases (
In-Reply-To: <20051116185138.GA22831@uio.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