Re: Conflict handling for COPY FROM

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org,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-19 12:47:23
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On February 19, 2019 3:05:37 AM PST, Surafel Temesgen <surafel3000(at)gmail(dot)com> wrote:
>On Sat, Feb 16, 2019 at 8:24 AM Andres Freund <andres(at)anarazel(dot)de>
>> Hi,
>> On 2018-08-23 17:11:04 +0300, Surafel Temesgen wrote:
>> > COPY ... WITH ON CONFLICT LOG maximum_error, LOG FILE NAME '…';
>> This doesn't seem to address Robert's point that a log file requires
>> be super user only, which seems to restrict the feature more than
>> necessary?
>> - Andres
>I think having write permission on specified directory is enough.
>we use out put file name in COPY TO similarly.

Err, what? Again, that requires super user permissions (in contrast to copy from/to stdin/out). Backends run as the user postgres runs under - it will always have write permissions to at least the entire data directory. I think not addressing this just about guarantees the feature will be rejected.

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 Andrew Dunstan 2019-02-19 12:51:27 Re: [Bug Fix] ECPG: could not use set xxx to default statement
Previous Message Kyotaro HORIGUCHI 2019-02-19 12:40:07 Re: shared-memory based stats collector