pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Smith <gsmith@gregsmith.com>
To: pgsql-performance@postgresql.org
Subject: Re: DRBD and Postgres: how to improve the perfomance?
Date: Mon, 10 Sep 2007 00:06:40 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0709092339330.8403@westnet.com> (raw)
In-Reply-To: <46E2D5A9.3060304@commandprompt.com>
References: <2C070D1C3970467FF64F6B6A@imhotep.credativ.de>
	<1189232904.4281.19.camel@ebony.site>
	<87k5r1zd52.fsf@oxford.xeocode.com>
	<46E2CAAF.50205@commandprompt.com>
	<87642lyuey.fsf@oxford.xeocode.com>
	<46E2D5A9.3060304@commandprompt.com>

On Sat, 8 Sep 2007, Joshua D. Drake wrote:

> You would have to have lightning handed by God to your server to have a 
> total power failure without proper shutdown in the above scenario.

Do you live somewhere without thunderstorms?  This is a regular event in 
this part of the world during the summer.  It happened to me once this 
year and once last; lost count for previous ones.  In both of the recent 
cases it's believed the servers were burned from the Ethernet side because 
somewhere in the network was a poor switch that wasn't isolated well 
enough from the grid when the building was hit.  Lightning is tricky that 
way; cable TV and satellite wiring are also weak links that way.

I didn't feel too bad about last year's because the building next door 
burned to the ground after being hit within a few seconds of mine, so the 
fact that I had some server repair didn't seem like too much of a hardship 
in comparison.  The system was down until the fire department had put out 
the blaze and I was allowed back into the building though.  Good thing my 
cell phone works in the server room; that phone call asking "are you aware 
the building is being evacuated?" is always a fun one.

I'm not saying God hates you as much as me, because the fact that you've 
made this statement says it's clearly not the case, just that a plan 
presuming he's your buddy is a bad one.  The way you're characterizing 
this risk reminds me of when people quote the odds that they'll lose two 
disks within seconds of one another in a disk array as if it's impossible, 
something else which of course has also happened to me many times during 
my career.

--
* Greg "Lucky" Smith gsmith@gregsmith.com Baltimore, MD



view thread (28+ messages)  latest in thread

Message-ID: <Pine.GSO.4.64.0709092339330.8403@westnet.com>
Permalink:  ../Pine.GSO.4.64.0709092339330.8403@westnet.com/
Also on:    postgresql.org/message-id/Pine.GSO.4.64.0709092339330.8403@westnet.com

 · 

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: gsmith@gregsmith.com
  Subject: Re: DRBD and Postgres: how to improve the perfomance?
  In-Reply-To: <Pine.GSO.4.64.0709092339330.8403@westnet.com>

* 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