Re: Conflict handling for COPY FROM - Mailing list pgsql-hackers

From Surafel Temesgen
Subject Re: Conflict handling for COPY FROM
Date
Msg-id CALAY4q-hWwbg-P1=oJcVT1jTHj_g+JxJ_0JNe4MdYKz8RvUF=g@mail.gmail.com
Whole thread Raw
In response to Re: Conflict handling for COPY FROM  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Conflict handling for COPY FROM
Re: Conflict handling for COPY FROM
List pgsql-hackers

Hello,

The attached patch add error handling for
Extra data

missing data

invalid oid

null oid and 

row count mismatch

And the record that field on the above case write to the file with appended error message in it and in case of unique violation or exclusion constraint violation error the failed record write as it is because the case of the error can not be identified specifically

The new syntax became :

COPY ... WITH ON CONFLICT LOG maximum_error, LOG FILE NAME '…';


Regards

Surafel

Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Memory leak with CALL to Procedure with COMMIT.
Next
From: Amit Langote
Date:
Subject: Re: Make executor's Range Table an array instead of a List