Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au>, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit
Date: 2008-03-12 15:47:20
Message-ID: 2e78013d0803120847k2e8afbedrc39e29e5194d3c6e@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-patchespgsql-performance
On Wed, Mar 12, 2008 at 7:13 PM, Heikki Linnakangas
<heikki(at)enterprisedb(dot)com> wrote:
>
>
>  Yep, patch attached. I also changed xactGetCommittedChildren to return
>  the original array instead of copying it, as Alvaro suggested.
>

Any comments on the flag based approach I suggested earlier ? Am I
missing some normal scenario where it won't work well ?

Thanks,
Pavan

-- 
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2008-03-12 15:57:19
Subject: Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit
Previous:From: Enrico SirolaDate: 2008-03-12 15:25:29
Subject: 8.3 write performance

pgsql-patches by date

Next:From: Tom LaneDate: 2008-03-12 15:57:19
Subject: Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit
Previous:From: Tom LaneDate: 2008-03-12 14:35:12
Subject: Re: [NOVICE] encoding problems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group