| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, "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:01:50 |
| Message-ID: | 200802051801.52963.dfontaine@hi-media.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Le mardi 05 février 2008, Simon Riggs a écrit :
> It runs a stream of COPY statements, so only first would be optimized
> with the "empty table optimization".
The number of rows per COPY statement is configurable, so provided you have an
estimation of the volume to import (wc -l), you could tweak this number for
lowering the stream (down to 1 COPY maybe)...
But basically a COPY run should be kept in memory (and we're talking about
high volumes here) and in case of error processing you'd want it not that
huge after all...
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2008-02-05 17:15:25 | Re: Benchmark Data requested |
| Previous Message | Matthew | 2008-02-05 16:18:10 | Re: Benchmark Data requested |