Re: Possible Redundancy/Performance Solution - Mailing list pgsql-performance

From Dennis Muhlestein
Subject Re: Possible Redundancy/Performance Solution
Date
Msg-id fvqj5j$5v5$1@news.hub.org
Whole thread Raw
In response to Re: Possible Redundancy/Performance Solution  (Greg Smith <gsmith@gregsmith.com>)
Responses Re: Possible Redundancy/Performance Solution  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Re: Possible Redundancy/Performance Solution  (Greg Smith <gsmith@gregsmith.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: "Josh Cole"
Date:
Subject: pgfouine - commit details?
Next
From: "Guillaume Smet"
Date:
Subject: Re: pgfouine - commit details?