From: Scott Marlowe <scott.marlowe@gmail.com>
To: Thomas Finneid <tfinneid@student.matnat.uio.no>
Cc: Scott Carey <scott@richrelevance.com>
Cc: Craig Ringer <craig@postnewspapers.com.au>
Cc: pgsql-performance@postgresql.org
Subject: Re: slow update of index during insert/copy
Date: Mon, 1 Sep 2008 14:49:38 -0600
Message-ID: <dcc563d10809011349q2d0e06c6g61197d9b8cf26ca0@mail.gmail.com> (raw)
In-Reply-To: <dcc563d10809011342i55d32d23la4604e71d19dfdb0@mail.gmail.com>
References: <48BA9D65.2020001@ifi.uio.no>
<48BB4A2D.9080404@postnewspapers.com.au>
<48BBD22E.4090308@ifi.uio.no>
<dcc563d10809011051s558f8a7bp5beb0dbe181721e4@mail.gmail.com>
<a1ec7d000809011146x456b942eof33627c63f8a021a@mail.gmail.com>
<48BC5178.60906@ifi.uio.no>
<dcc563d10809011342i55d32d23la4604e71d19dfdb0@mail.gmail.com>
On Mon, Sep 1, 2008 at 2:42 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> dialog box saying this is a bad idea. Now, if it would take you a day
> of downtime to get a dev database back in place and running after a
> power loss, then the bbu may be worth the $200 or so.
I just wanted to comment that depending on how many people depend on
the development machine to get their job done the more easy it is to
justify a battery.
If 20 people rely on a machine to do their job, just multiply their
hourly cost to the company times your restore time for a figure that
will be several times higher than the cost of the battery.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: scott.marlowe@gmail.com, tfinneid@student.matnat.uio.no, scott@richrelevance.com, craig@postnewspapers.com.au
Subject: Re: slow update of index during insert/copy
In-Reply-To: <dcc563d10809011349q2d0e06c6g61197d9b8cf26ca0@mail.gmail.com>
References: <48BA9D65.2020001@ifi.uio.no> <48BB4A2D.9080404@postnewspapers.com.au> <48BBD22E.4090308@ifi.uio.no> <dcc563d10809011051s558f8a7bp5beb0dbe181721e4@mail.gmail.com> <a1ec7d000809011146x456b942eof33627c63f8a021a@mail.gmail.com> <48BC5178.60906@ifi.uio.no> <dcc563d10809011342i55d32d23la4604e71d19dfdb0@mail.gmail.com> <dcc563d10809011349q2d0e06c6g61197d9b8cf26ca0@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