pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Boreham <david_list@boreham.org>
To: pgsql-performance@postgresql.org
Subject: Re: hardware advice
Date: Fri, 28 Sep 2012 09:57:16 -0600
Message-ID: <5065C8DC.5020305@boreham.org> (raw)
In-Reply-To: <CAFwQ8reo-nBmb_PvXAH6BYzLxmkE2UhnNZVfdwV-VbAPqKzvzQ@mail.gmail.com>
References: <5064A4DC.5090304@turnkey.bz>
	<CAFwQ8rf4Cnt9Ksd+3GbkkWtZ3NM+hYukd1gKRLmsihXnKzVteA@mail.gmail.com>
	<5064AD5C.4010403@boreham.org>
	<5064AF52.3070706@turnkey.bz>
	<5064B34D.2000105@boreham.org>
	<CAFwQ8reo-nBmb_PvXAH6BYzLxmkE2UhnNZVfdwV-VbAPqKzvzQ@mail.gmail.com>

On 9/28/2012 9:46 AM, Craig James wrote:
> Your best warranty would be to have the confidence to do your own
> repairs, and to have the parts on hand.  I'd seriously consider
> putting your own system together.  Maybe go to a few sites with
> pre-configured machines and see what parts they use.  Order those,
> screw the thing together yourself, and put a spare of each critical
> part on your shelf.
>
This is what I did for years, but after taking my old parts collection 
to the landfill a few times, realized I may as well just buy N+1 
machines and keep zero spares on the shelf. That way I get a spare 
machine available for use immediately, and I know the parts are working 
(parts on the shelf may be defective). If something breaks, I use the 
spare machine until the replacement parts arrive.

Note in addition that a warranty can be extremely useful in certain 
organizations as a vehicle of blame avoidance (this may be its primary 
purpose in fact). If I buy a bunch of machines that turn out to have 
buggy NICs, well that's my fault and I can kick myself since I own the 
company, stay up late into the night reading kernel code, and buy new 
NICs. If I have an evil Dilbertian boss, then well...I'd be seriously 
thinking about buying Dell boxes in order to blame Dell rather than 
myself, and be able to say "everything is warrantied" if badness goes 
down. Just saying...






view thread (60+ messages)  latest in thread

Message-ID: <5065C8DC.5020305@boreham.org>
Permalink:  ../5065C8DC.5020305@boreham.org/
Also on:    postgresql.org/message-id/5065C8DC.5020305@boreham.org

 · 

reply

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: david_list@boreham.org
  Subject: Re: hardware advice
  In-Reply-To: <5065C8DC.5020305@boreham.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