Document the fact that COPY always uses the client encoding.

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 703951de8031b7e0b793439abd8a05cdd2f38cb9..bd1b94ae3956db1c8aa227f72492c074b511a37a 100644 (file)
--- 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.80 2007/04/18 02:28:22 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.81 2008/01/16 22:07:04 adunstan Exp $
 PostgreSQL documentation
 -->
 
@@ -353,6 +353,13 @@ COPY <replaceable class="parameter">count</replaceable>
     using <command>COPY TO</>.
    </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.
+   </para>
+
    <para>
     <command>COPY</command> stops operation at the first error. This
     should not lead to problems in the event of a <command>COPY
@@ -363,6 +370,7 @@ COPY <replaceable class="parameter">count</replaceable>
     happened well into a large copy operation. You might wish to invoke
     <command>VACUUM</command> to recover the wasted space.
    </para>
+
  </refsect1>
  
  <refsect1>