Re: Conflict handling for COPY FROM
От | Andrew Dunstan |
---|---|
Тема | Re: Conflict handling for COPY FROM |
Дата | |
Msg-id | 62827e86-ded2-a68e-dfdc-1454a38a704d@2ndQuadrant.com обсуждение исходный текст |
Ответ на | Re: Conflict handling for COPY FROM (Surafel Temesgen <surafel3000@gmail.com>) |
Ответы |
Re: Conflict handling for COPY FROM
|
Список | pgsql-hackers |
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. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: