From: Raj Mathur (राज माथुर) <raju@linux-delhi.org>
To: pgsql-sql@postgresql.org
Subject: Re: Insane behaviour in 8.3.3
Date: Fri, 15 Jun 2012 22:58:39 +0530
Message-ID: <201206152258.39760.raju@linux-delhi.org> (raw)
In-Reply-To: <CAEV0TzAeR2+Hir-+03HmN4mt60Ppwp_QQJ49vV1P0z-fvSMgHg@mail.gmail.com>
References: <201206141139.35601.achill@matrix.gatewaynet.com>
<201206151124.45021.achill@matrix.gatewaynet.com>
<CAEV0TzAeR2+Hir-+03HmN4mt60Ppwp_QQJ49vV1P0z-fvSMgHg@mail.gmail.com>
On Friday 15 Jun 2012, Samuel Gendler wrote:
> On Fri, Jun 15, 2012 at 1:24 AM, Achilleas Mantzios <
>
> achill@matrix.gatewaynet.com> wrote:
> > And i forgot to mention, minicom term emulation quality sucks, even
> > giving simple
> > shell commands is a PITA, upgrading the whole fleet would mean bast
> > case scenario
> > minimum 21K USD for the whole fleet + suspension of all other
> > activities for two months.
> > If physical travel was involved, the cost would be increased at
> > even higher levels.
>
> And what is the cost of data corruption on large numbers of systems?
> And how much to fix that, especially if multiple systems fail at the
> same time? Some things aren't free. $21K in exchange for NOT having
> had to keep systems up to date for 4 years seems like a decent
> trade.
While I agree in principle with what you're saying, this specific
comparison would be better stated as "What is the cost of data
corruption multiplied by the risk of that corruption occurring?"
The cost of upgrading is known and unavoidable. The cost of data
corruption, while probably higher (unless Achilles has an effective
backup/restore system), needs to be factored by its probability of
occurance.
Of course, neither you nor I are in Achilles' shoes, so trying to figure
out where they pinch is academic at best.
Regards,
-- Raj
--
Raj Mathur || raju@kandalaya.org || GPG:
http://otheronepercent.blogspot.com || http://kandalaya.org || CC68
It is the mind that moves || http://schizoid.in || D17F
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-sql@postgresql.org
Cc: raju@linux-delhi.org
Subject: Re: Insane behaviour in 8.3.3
In-Reply-To: <201206152258.39760.raju@linux-delhi.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