| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, "Jignesh K(dot) Shah" <J(dot)K(dot)Shah(at)sun(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com> |
| Subject: | Re: Benchmark Data requested |
| Date: | 2008-02-05 17:32:33 |
| Message-ID: | 1202232753.4252.789.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jignesh K. Shah | 2008-02-05 18:47:13 | Re: Benchmark Data requested |
| Previous Message | Dimitri Fontaine | 2008-02-05 17:15:25 | Re: Benchmark Data requested |