Re: [PATCH] COPY vs \copy HINT

From: Christoph Berg <myon(at)debian(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] COPY vs \copy HINT
Date: 2016-09-06 20:19:48
Message-ID: 20160906201948.brhvg57zoiydvb4z@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Tom Lane 2016-09-06 <17637(dot)1473192771(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2016-09-06 20:21:49 Re: patch: function xmltable
Previous Message Tom Lane 2016-09-06 20:19:30 Re: [PATCH] Alter or rename enum value