From: | "Jignesh K(dot) Shah" <J(dot)K(dot)Shah(at)Sun(dot)COM> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, pgsql-performance(at)postgresql(dot)org, Greg Smith <gsmith(at)gregsmith(dot)com> |
Subject: | Re: Benchmark Data requested |
Date: | 2008-02-05 18:47:13 |
Message-ID: | 47A8AF31.8070304@sun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
That sounds cool to me too..
How much work is to make pg_bulkload to work on 8.3? An Integrated
version is certainly more beneficial.
Specially I think it will also help for other setups like TPC-E too
where this is a problem.
Regards,
Jignesh
Simon Riggs wrote:
> On Tue, 2008-02-05 at 18:15 +0100, Dimitri Fontaine wrote:
>
>> Le mardi 05 février 2008, Simon Riggs a écrit :
>>
>>> I'll look at COPY FROM internals to make this faster. I'm looking at
>>> this now to refresh my memory; I already had some plans on the shelf.
>>>
>> Maybe stealing some ideas from pg_bulkload could somewhat help here?
>> http://pgfoundry.org/docman/view.php/1000261/456/20060709_pg_bulkload.pdf
>>
>
>
>> IIRC it's mainly about how to optimize index updating while loading data, and
>> I've heard complaints on the line "this external tool has to know too much
>> about PostgreSQL internals to be trustworthy as non-core code"... so...
>>
>
> Yeh, the batch index updates are a cool feature. Should be able to do
> that internally also.
>
> Not going to try the no-WAL route again though. If we can get it running
> efficiently and in parallel, then that will be OK.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-02-05 19:48:26 | Re: Benchmark Data requested |
Previous Message | Simon Riggs | 2008-02-05 17:32:33 | Re: Benchmark Data requested |