Re: [PATCH] COPY vs \copy HINT

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [PATCH] COPY vs \copy HINT
Дата
Msg-id 17637.1473192771@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [PATCH] COPY vs \copy HINT  (Craig Ringer <craig@2ndquadrant.com>)
Ответы Re: [PATCH] COPY vs \copy HINT  (Christoph Berg <myon@debian.org>)
Список pgsql-hackers
Craig Ringer <craig@2ndquadrant.com> writes:
> 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.

I think my original wording is pretty hopeless for the single-machine
case: "COPY copies to a file on the PostgreSQL server, not on the client".
If the server and client are the same machine, that's content-free.

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?
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: [PATCH] Alter or rename enum value
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: patch: function xmltable