Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 98AFC650111 for ; Mon, 1 Sep 2008 17:49:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 45602-04 for ; Mon, 1 Sep 2008 17:49:37 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.225]) by postgresql.org (Postfix) with ESMTP id 5BB7D64FF4F for ; Mon, 1 Sep 2008 17:49:39 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id b25so2790265rvf.43 for ; Mon, 01 Sep 2008 13:49:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=nRmudBmu6cKEGG3cRCNDKbbYzz/XMsU0E8dsr9WLCho=; b=MlsaBxGGYhxF0UKaF7O6jhE2jPj9wKK383NV7BGJsFwiLO7BW3YQ3stoHc634SB2E9 Yo2au6kWMSrLfmGWANZpu/qnhwNKOK6PxO87mLhrjZMi1SI8VKdBal2u7je9V8UW0GfI hyS8Tjq16OlI5L92SH/YU7Bhp4N3yull1uWKc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=shPBiy0bdH/mHCJHDAaIr2WxeBqZBDDAwbkkWaUoEXDxYvbgOuVc5WuC1I9UxQF1/e QtMeczcqSU3YVRIcx3p06f7v9Df/YmHWr1j1dLHsNhEhkcEEWWdwyLomgGBbBDU8vsdp DSDNgzX+2LBd55V1vKyKKcKb9Nu24yfMvd3tc= Received: by 10.141.189.4 with SMTP id r4mr3672265rvp.226.1220302178172; Mon, 01 Sep 2008 13:49:38 -0700 (PDT) Received: by 10.140.248.12 with HTTP; Mon, 1 Sep 2008 13:49:38 -0700 (PDT) Message-ID: Date: Mon, 1 Sep 2008 14:49:38 -0600 From: "Scott Marlowe" To: "Thomas Finneid" Subject: Re: slow update of index during insert/copy Cc: "Scott Carey" , "Craig Ringer" , pgsql-performance@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48BA9D65.2020001@ifi.uio.no> <48BB4A2D.9080404@postnewspapers.com.au> <48BBD22E.4090308@ifi.uio.no> <48BC5178.60906@ifi.uio.no> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/17 X-Sequence-Number: 31330 On Mon, Sep 1, 2008 at 2:42 PM, Scott Marlowe 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.