Re: Conflict handling for COPY FROM

From: Surafel Temesgen <surafel3000(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Conflict handling for COPY FROM
Date: 2018-08-23 14:11:04
Message-ID: CALAY4q-hWwbg-P1=oJcVT1jTHj_g+JxJ_0JNe4MdYKz8RvUF=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: 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 Content-Type Size
conflict-handling-onCopy-from-v2.patch text/x-patch 14.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2018-08-23 14:26:50 Re: Make executor's Range Table an array instead of a List
Previous Message Peter Eisentraut 2018-08-23 13:34:25 Re: Memory leak with CALL to Procedure with COMMIT.