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 @@
 
 
@@ -353,6 +353,13 @@ COPY count
     using COPY TO.
    
 
+   
+    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.
+   
+
    
     COPY stops operation at the first error. This
     should not lead to problems in the event of a COPY
@@ -363,6 +370,7 @@ COPY count
     happened well into a large copy operation. You might wish to invoke
     VACUUM to recover the wasted space.
    
+