Re: Conflict handling for COPY FROM

From: Surafel Temesgen <surafel3000(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
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 11:05:37
Message-ID: CALAY4q8vD-FY--nWDVv509-95NgTEbL6UGY-MEY0+-J540fSpA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 16, 2019 at 8:24 AM Andres Freund <andres(at)anarazel(dot)de> wrote:

> 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 to
> 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.

regards
Surafel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2019-02-19 11:21:22 Re: [Bug Fix] ECPG: could not use set xxx to default statement
Previous Message Surafel Temesgen 2019-02-19 10:51:53 Re: Conflict handling for COPY FROM