Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 89ABB64FCEB for ; Fri, 5 Sep 2008 05:09:21 -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 04206-09 for ; Fri, 5 Sep 2008 05:09:14 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-out2.uio.no (mail-out2.uio.no [129.240.10.58]) by postgresql.org (Postfix) with ESMTP id 0A66464FCBA for ; Fri, 5 Sep 2008 05:09:10 -0300 (ADT) Received: from mail-mx6.uio.no ([129.240.10.47]) by mail-out2.uio.no with esmtp (Exim 4.69) (envelope-from ) id 1KbWNP-0007hA-Lk; Fri, 05 Sep 2008 10:09:07 +0200 Received: from 165.84-49-232.nextgentel.com ([84.49.232.165] helo=[10.0.0.10]) by mail-mx6.uio.no with esmtpsa (TLSv1:AES256-SHA:256) user tfinneid (Exim 4.69) (envelope-from ) id 1KbWNP-0002p4-8b; Fri, 05 Sep 2008 10:09:07 +0200 Message-ID: <48C0E931.4080703@ifi.uio.no> Date: Fri, 05 Sep 2008 10:09:21 +0200 From: Thomas Finneid User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: Greg Smith CC: pgsql-performance@postgresql.org Subject: Re: slow update of index during insert/copy References: <48BA9D65.2020001@ifi.uio.no> <48BB4A2D.9080404@postnewspapers.com.au> <48BBD22E.4090308@ifi.uio.no> <48BCDF9C.5020906@ifi.uio.no> <48BFA118.9010701@ifi.uio.no> In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-UiO-SPF-Received: X-UiO-Spam-info: not spam, SpamAssassin (score=-4.5, required=5.0, autolearn=disabled, TVD_RCVD_IP=0.502, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 6708FC43E91A299184BE953D2D2B6FF2947456D5 X-UiO-SPAM-Test: remote_host: 84.49.232.165 spam_score: -44 maxlevel 200 minaction 2 bait 0 mail/h: 1 total 74 max/h 6 blacklist 0 greylist 0 ratelimit 0 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/69 X-Sequence-Number: 31382 Greg Smith wrote: > In practice, the "ordered" > mode (the default for ext3) seems sufficient to prevent database > corruption. There is a substantial performance hit to running in full > journal mode like you're doing; where do you see which mode I am running in? I havent specified any modes in any config or commands, so I am assuming its using ext3 defaults, which I am assuming is "ordered". regards