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

From Robert Haas
Subject Re: Conflict handling for COPY FROM
Date
Msg-id CA+TgmoYo2fLSHOaM-3jsV2ONM8-_tuoU2RPme9dBpbggC2==yg@mail.gmail.com
Whole thread Raw
In response to Conflict handling for COPY FROM  (Surafel Temesgen <surafel3000@gmail.com>)
Responses Re: Conflict handling for COPY FROM
Re: Conflict handling for COPY FROM
List pgsql-hackers
On Sat, Aug 4, 2018 at 9:10 AM Surafel Temesgen <surafel3000@gmail.com> wrote:

In order to prevent extreme condition the patch also add a new GUC variable called copy_max_error_limit that control the amount of error to swallow before start to error and new failed record file options for copy to write a failed record so the user can examine it.


Why should this be a GUC rather than a COPY option?

In fact, try doing all of this by adding more options to COPY rather than new syntax. 

COPY ... WITH (ignore_conflicts 1000, ignore_logfile '...')

It kind of stinks to use a log file written by the server as the dup-reporting channel though. That would have to be superuser-only.

...Robert
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: ALTER TABLE on system catalogs
Next
From: Ashutosh Bapat
Date:
Subject: Re: TupleTableSlot abstraction