From 1180b640759b32d63aa95fe8c4a44bec06c65ccb Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 23 Feb 2010 05:17:33 +0000
Subject: [PATCH] Make documentation more direct about the handling of COPY
 files based on the client encoding.

---
 doc/src/sgml/ref/copy.sgml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index ae6e250e46..a8e70a581d 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.93 2010/02/17 04:19:39 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.94 2010/02/23 05:17:33 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -367,10 +367,10 @@ COPY <replaceable class="parameter">count</replaceable>
    </para>
 
    <para>
-    Input data is interpreted according to the current client encoding,
-    and output data is encoded in the the current client encoding, even
-    if the data does not pass through the client but is read from or
-    written to a file.
+    <command>COPY</command> always processes data according to the
+    current client encoding, even if the data does not pass through
+    the client but is read from or written to a file directly by the
+    server.
    </para>
 
    <para>
-- 
2.40.0