Re: [PATCH] COPY vs \copy HINT - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: [PATCH] COPY vs \copy HINT
Date
Msg-id CAMsr+YGsf9zqdZuiqW2x_MG-KC29DREXRds1yrtFSdYz+oc7Og@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] COPY vs \copy HINT  (Christoph Berg <myon@debian.org>)
Responses Re: [PATCH] COPY vs \copy HINT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 5 September 2016 at 16:32, Christoph Berg <myon@debian.org> wrote:

> The part about the server permissions might be useful to hint at.

> What about
>
>      "COPY TO instructs the PostgreSQL server to write to a file on the server. "
>      "You may want a client-side facility such as psql's \\copy."
>
>      "COPY FROM instructs the PostgreSQL server to read from a file on the server. "
>      "You may want a client-side facility such as psql's \\copy."
>
> This stresses more explicitly that the file is opened by the server
> process. (I'm not particularly happy that it says "server" in there
> twice, but couldn't think of anything else.)

Tom, any preference here?

I'm probably inclined to go for your original wording and accept that
it's just too hard to hint at the client/server process split in a
single short message.

-- Craig Ringer                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Stopping logical replication protocol
Next
From: Kouhei Kaigai
Date:
Subject: Re: PassDownLimitBound for ForeignScan/CustomScan