From: Dennis Muhlestein <djmuhlestein@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Possible Redundancy/Performance Solution
Date: Tue, 06 May 2008 15:39:02 -0600
Message-ID: <fvqj5j$5v5$1@news.hub.org> (raw)
In-Reply-To: <Pine.GSO.4.64.0805061625150.11474@westnet.com>
References: <fvq189$2ej4$1@news.hub.org>
<Pine.GSO.4.64.0805061316340.3589@westnet.com>
<fvq854$ocq$1@news.hub.org>
<Pine.GSO.4.64.0805061625150.11474@westnet.com>
Greg Smith wrote:
> On Tue, 6 May 2008, Dennis Muhlestein wrote:
>
> Since disks are by far the most likely thing to fail, I think it would
> be bad planning to switch to a design that doubles the chance of a disk
> failure taking out the server just because you're adding some
> server-level redundancy. Anybody who's been in this business for a
> while will tell you that seemingly improbable double failures happen,
> and if were you'd I want a plan that survived a) a single disk failure
> on the primary and b) a single disk failure on the secondary at the same
> time.
>
> Let me strengthen that--I don't feel comfortable unless I'm able to
> survive a single disk failure on the primary and complete loss of the
> secondary (say by power supply failure), because a double failure that
> starts that way is a lot more likely than you might think. Especially
> with how awful hard drives are nowadays.
Those are good points. So you'd go ahead and add the pgpool in front
(or another redundancy approach, but then use raid1,5 or perhaps 10 on
each server?
-Dennis
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: djmuhlestein@gmail.com
Subject: Re: Possible Redundancy/Performance Solution
In-Reply-To: <fvqj5j$5v5$1@news.hub.org>
* 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