Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 1C1F02E0136 for ; Tue, 11 Mar 2008 06:58:37 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 07040-07 for ; Tue, 11 Mar 2008 06:58:29 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id D08CB2E0157 for ; Tue, 11 Mar 2008 06:58:28 -0300 (ADT) thread-index: AciDXoctuHpeY7LJS0Cey3U1UUX4yw== Received: from [172.24.32.184] ([62.232.55.118]) by mail01.enterprisedb.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 11 Mar 2008 05:58:59 -0400 Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133 Message-ID: <47D657BC.40409@enterprisedb.com> Date: Tue, 11 Mar 2008 09:58:20 +0000 From: "Heikki Linnakangas" Organization: EnterpriseDB User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20080110) MIME-Version: 1.0 To: "Simon Riggs" Cc: "Craig Ringer" , Subject: Re: Very slow (2 tuples/second) sequential scan afterbulk insert; speed returns to ~500 tuples/second after commit References: <47D505AF.4040101@postnewspapers.com.au> <47D5150C.8090802@enterprisedb.com> <1205186427.4269.179.camel@ebony.site> In-Reply-To: <1205186427.4269.179.camel@ebony.site> Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 11 Mar 2008 09:58:59.0718 (UTC) FILETIME=[871F0260:01C8835E] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/225 X-Sequence-Number: 29179 Simon Riggs wrote: > On Mon, 2008-03-10 at 11:01 +0000, Heikki Linnakangas wrote: >> According >> to oprofile, all the time is spent in TransactionIdIsInProgress. > > I recently submitted a patch to optimise this. Your comments would be > welcome on the patch. You mean this one: http://archives.postgresql.org/pgsql-patches/2008-02/msg00008.php ? Unfortunately that patch won't help in this case. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com