From: Scott Marlowe <scott.marlowe@gmail.com>
To: jd@commandprompt.com
Cc: Jan-Ivar Mellingen <jan-ivar.mellingen@alreg.no>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: linux standard layout
Date: Tue, 9 Mar 2010 14:25:26 -0700
Message-ID: <dcc563d11003091325t6b659ef4x34222ed793022aa2@mail.gmail.com> (raw)
In-Reply-To: <1268168772.31596.147.camel@jd-desktop.unknown.charter.com>
References: <Pine.GSO.4.64.1003082243200.10671@coe.tamu.edu>
<4B95E162.7060806@djs-consulting.com>
<3769.1268115316@sss.pgh.pa.us>
<4B96AD1B.7070601@alreg.no>
<dcc563d11003091235u23423b38if274b3220d13dff7@mail.gmail.com>
<1268168772.31596.147.camel@jd-desktop.unknown.charter.com>
On Tue, Mar 9, 2010 at 2:06 PM, Joshua D. Drake <jd@commandprompt.com> wrote:
> On Tue, 2010-03-09 at 13:35 -0700, Scott Marlowe wrote:
>
>> > In a nutshell, I am heartly recommending virtualization.
>>
>> In a nutshell, you are relying on luck that both heavy iron machines
>> can't lose power at the same time. Sure, it's a low possibility, but
>> it's still a real one.
>>
>
> Not luck. Percentage of risk.
They're both ways of saying you're rolling the dice. And in every
situation we're rolling the dice, it's just a question of how many and
how unlikely a particular outcome it. It's why we all have off-site
backups, and so on.
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-admin@postgresql.org
Cc: scott.marlowe@gmail.com, jd@commandprompt.com, jan-ivar.mellingen@alreg.no, tgl@sss.pgh.pa.us
Subject: Re: linux standard layout
In-Reply-To: <dcc563d11003091325t6b659ef4x34222ed793022aa2@mail.gmail.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