Re: [PERFORM] Very slow (2 tuples/second) sequentialscan after bulk insert; speed returns to ~500 tuples/second aftercommit - Mailing list pgsql-patches

From Heikki Linnakangas
Subject Re: [PERFORM] Very slow (2 tuples/second) sequentialscan after bulk insert; speed returns to ~500 tuples/second aftercommit
Date
Msg-id 47D6911C.3040605@enterprisedb.com
Whole thread Raw
In response to Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-patches
Alvaro Herrera wrote:
> Heikki Linnakangas wrote:
>
>> I couldn't let this case go, so I wrote a patch. I replaced the linked
>> list with an array that's enlarged at AtSubCommit_childXids when
>> necessary.
>
> Do you still need to palloc the return value from
> xactGetCommittedChildren?  Perhaps you can save the palloc/memcpy/pfree
> and just return the pointer to the array already in memory?

Yeah, good point. The callers just need to be modified not to pfree it.

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

pgsql-patches by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: TransactionIdIsInProgress() cache
Next
From: Alvaro Herrera
Date:
Subject: Re: TransactionIdIsInProgress() cache