| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Headland <pheadland(at)actuate(dot)com>, Adrian Klaver <aklaver(at)comcast(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: COPY command character set |
| Date: | 2010-02-23 06:00:36 |
| Message-ID: | 201002230600.o1N60ae13456@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)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. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-23 06:03:48 | Re: Sorting performance vs. MySQL |
| Previous Message | Tom Lane | 2010-02-23 05:57:29 | Re: COPY command character set |