11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.80 2007/04/18 02:28:22 momjian Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.81 2008/01/16 22:07:04 adunstan Exp $
33PostgreSQL documentation
44-->
55
@@ -353,6 +353,13 @@ COPY <replaceable class="parameter">count</replaceable>
353353 using <command>COPY TO</>.
354354 </para>
355355
356+ <para>
357+ Input data is interpreted according to the current client encoding,
358+ and output data is encoded in the the current client encoding, even
359+ if the data does not pass through the client but is read from or
360+ written to a file.
361+ </para>
362+
356363 <para>
357364 <command>COPY</command> stops operation at the first error. This
358365 should not lead to problems in the event of a <command>COPY
@@ -363,6 +370,7 @@ COPY <replaceable class="parameter">count</replaceable>
363370 happened well into a large copy operation. You might wish to invoke
364371 <command>VACUUM</command> to recover the wasted space.
365372 </para>
373+
366374 </refsect1>
367375
368376 <refsect1>