Re: Practical error logging for very large COPY statements

Tom Lane wrote:

>Simon Riggs <simon@2ndquadrant.com> writes:
>  
>
>>What I'd like to do is add an ERRORTABLE clause to COPY. The main
>>problem is how we detect a duplicate row violation, yet prevent it from
>>aborting the transaction.
>>    
>>
>
>If this only solves the problem of duplicate keys, and not any other
>kind of COPY error, it's not going to be much of an advance.
>  
>

Yeah, and I see errors from bad data as often as from violating 
constraints. Maybe the best way if we do something like this would be to 
have the error table contain a single text, or maybe bytea, field which 
contained the raw offending input line.

cheers

andrew