"CK Tan" <[EMAIL PROTECTED]> writes:
> COPY/INSERT are also bottlenecked on record at a time insertion into  
> heap, and in checking for pre-insert trigger, post-insert trigger and  
> constraints.

> To speed things up, we really need to special case insertions without  
> triggers and constraints, [probably allow for unique constraints],  

Do you have any profiling data to back up these assertions?  I haven't
noticed that firing zero tuples takes any visible percentage of COPY

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Reply via email to