mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Document the fact that COPY always uses the client encoding.

Browse Source
This commit is contained in:
Andrew Dunstan 2008-01-16 22:07:04 +00:00
parent 97e3a6e9c5
commit c7d7c15bb1
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/ref/copy.sgml
View File

@ -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>