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

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to