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

From Andres Freund
Subject Re: Conflict handling for COPY FROM
Date
Msg-id 82B3531E-082D-4882-A15E-25293F779569@anarazel.de
Whole thread Raw
In response to Re: Conflict handling for COPY FROM  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: Re: Conflict handling for COPY FROM  (David Steele <david@pgmasters.net>)
Re: Conflict handling for COPY FROM  (Surafel Temesgen <surafel3000@gmail.com>)
List pgsql-hackers

On February 20, 2019 6:05:53 AM PST, Andrew Dunstan <andrew.dunstan@2ndquadrant.com> wrote:
>
>On 2/20/19 8:01 AM, Surafel Temesgen wrote:
>>
>>
>> On Tue, Feb 19, 2019 at 3:47 PM Andres Freund <andres@anarazel.de
>> <mailto:andres@anarazel.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.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Delay locking partitions during INSERT and UPDATE
Next
From: Robert Haas
Date:
Subject: Re: propagating replica identity to partitions