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

From Christoph Berg
Subject Re: [PATCH] COPY vs \copy HINT
Date
Msg-id 20160906201948.brhvg57zoiydvb4z@msg.df7cb.de
Whole thread Raw
In response to Re: [PATCH] COPY vs \copy HINT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] COPY vs \copy HINT  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
Re: Tom Lane 2016-09-06 <17637.1473192771@sss.pgh.pa.us>
> Christoph's idea isn't bad.  We could tweak it to:
>
>     COPY TO instructs the PostgreSQL server process to write a file.
>
>     COPY FROM instructs the PostgreSQL server process to read a file.
>
> This seems to cover both the wrong-machine and wrong-process-identity
> cases, and as a bonus it might help if you've had a brain fade about
> which COPY direction is write vs. read.
>
> (I think we're all in agreement that the second sentence of the hint
> is fine, so leaving that out of it.)
>
> Comments?

I like your new version, it's crisp and transports the right message.

Christoph

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Alter or rename enum value
Next
From: Pavel Stehule
Date:
Subject: Re: patch: function xmltable