From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: DRBD and Postgres: how to improve the perfomance?
Date: Mon, 10 Sep 2007 00:54:37 -0400
Message-ID: <17162.1189400077@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.GSO.4.64.0709092339330.8403@westnet.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>
<Pine.GSO.4.64.0709092339330.8403@westnet.com>
Greg Smith <gsmith@gregsmith.com> writes:
> 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.
Yeah. I've lost half a dozen modems of varying generations, a server
motherboard, a TiVo, a couple of VCRs, and miscellaneous other equipment
from strikes near my house --- none closer than a couple blocks away.
I don't really care to think about what would still work after a direct
hit, despite the whole-house surge suppressor at the meter and the local
suppressor on each circuit and the allegedly surge-proof UPSes powering
all the valuable stuff. I've also moved heavily into wireless local
net to eliminate any direct electrical connections between machines that
are not on the same power circuit (the aforesaid burned motherboard
taught me that particular lesson). And yet I still fear every time a
thunderstorm passes over.
Then of course there are the *other* risks, such as the place burning to
the ground, or getting drowned by a break in the city reservoir that's
a couple hundred yards up the hill (but at least I needn't worry about
any nearby rivers rising, as I'm well above them). Or maybe being
burgled by Oracle employees who are specifically after my backup tapes.
If you ain't got a backup plan, you *will* lose data. Imagining that
there is one perfect technological solution to this problem is the very
fastest way to lose.
regards, tom lane
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: tgl@sss.pgh.pa.us, gsmith@gregsmith.com
Subject: Re: DRBD and Postgres: how to improve the perfomance?
In-Reply-To: <17162.1189400077@sss.pgh.pa.us>
* 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