Re: [PATCH] COPY vs \copy HINT

From: Christoph Berg <myon(at)debian(dot)org>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] COPY vs \copy HINT
Date: 2016-08-12 08:34:37
Message-ID: 20160812083436.lprlra2zh2w4mvmk@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Craig Ringer 2016-08-12 <CAMsr+YEqtD97qPEzQDqrCt5QiqPbWP_X4hmvy2pQzWC0GWiyPA(at)mail(dot)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2016-08-12 08:40:13 Re: Btree Index on PostgreSQL and Wiredtiger (MongoDB3.2)
Previous Message Masahiko Sawada 2016-08-12 08:26:24 Re: new autovacuum criterion for visible pages