Re: COPY command character set - Mailing list pgsql-general

From Bruce Momjian
Subject Re: COPY command character set
Date
Msg-id 201002230600.o1N60ae13456@momjian.us
Whole thread Raw
In response to Re: COPY command character set  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: COPY command character set  ("Peter Headland" <pheadland@actuate.com>)
List pgsql-general
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I have updated the documentation to be more direct about COPY encoding
> > behavior.  Patch attached and applied.
>
> Uh, why exactly do you find that better?  "Processes data" seems a lot
> vaguer to me than the previous wording.  I certainly don't think that
> this does much to address Peter's original complaint.

I thought the problem was that we said "input", then "output" and then
got to the point about the server, and I thought the reader just stopped
reading that far, so I tried to shorten it so the idea was sooner, and I
mentioned "server" at the end.  It might not be better, but I tried.

We don't want to highlight the input/output, we want to highlight that
all input and output are controlled by the client encoding.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com
  PG East:  http://www.enterprisedb.com/community/nav-pg-east-2010.do
  + If your life is a hard drive, Christ can be your backup. +

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: COPY command character set
Next
From: Tom Lane
Date:
Subject: Re: Sorting performance vs. MySQL