Re: [PATCH] COPY vs \copy HINT
От | Christoph Berg |
---|---|
Тема | Re: [PATCH] COPY vs \copy HINT |
Дата | |
Msg-id | 20160812083436.lprlra2zh2w4mvmk@msg.df7cb.de обсуждение исходный текст |
Ответ на | [PATCH] COPY vs \copy HINT (Craig Ringer <craig@2ndquadrant.com>) |
Ответы |
Re: [PATCH] COPY vs \copy HINT
|
Список | pgsql-hackers |
Re: Craig Ringer 2016-08-12 <CAMsr+YEqtD97qPEzQDqrCt5QiqPbWP_X4hmvy2pQzWC0GWiyPA@mail.gmail.com> > I think we should emit a HINT here, something like: > > ERROR: could not open file "D:\CBS_woningcijfers_2014.csv" for reading: No > such file or directory' > HINT: Paths for COPY are on the PostgreSQL server, not the client. You may > want psql's \copy or a driver COPY ... FROM STDIN wrapper +1 on the idea. > postgres=# COPY x TO '/root/nopermissions'; > ERROR: could not open file "/root/nopermissions" for writing: Permission > denied > HINT: Paths for COPY are on the PostgreSQL server, not the client. You may > want psql's \copy or a driver COPY ... FROM STDIN wrapper TO STDOUT. Also, I vaguely get what you wanted to say with "a driver ... wrapper", but it's pretty nonsensical if one doesn't know about the protocol details. I don't have a better suggestion now, but I think it needs rephrasing. Christoph
В списке pgsql-hackers по дате отправления: