Re: Conflict handling for COPY FROM

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org,Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>,Surafel Temesgen <surafel3000(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>,PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Conflict handling for COPY FROM
Date: 2019-02-20 16:03:54
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On February 20, 2019 6:05:53 AM PST, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
>On 2/20/19 8:01 AM, Surafel Temesgen wrote:
>> On Tue, Feb 19, 2019 at 3:47 PM Andres Freund <andres(at)anarazel(dot)de
>> <mailto:andres(at)anarazel(dot)de>> wrote:
>> Err, what? Again, that requires super user permissions (in
>> contrast to copy from/to stdin/out). Backends run as the user
>> postgres runs under
>> okay i see it now and modified the patch similarly 
>Why log to a file at all? We do have, you know, a database handy, where
>we might more usefully log errors. You could usefully log the offending
>row as an array of text, possibly.

Or even just return it as a row. CopyBoth is relatively widely supported these days.

Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2019-02-20 16:09:19 Re: propagating replica identity to partitions
Previous Message Tom Lane 2019-02-20 16:03:32 Re: Delay locking partitions during INSERT and UPDATE