aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2010-02-23 05:17:33 +0000
committerBruce Momjian <bruce@momjian.us>2010-02-23 05:17:33 +0000
commit1180b640759b32d63aa95fe8c4a44bec06c65ccb (patch)
tree13484797f79f7cc5845bea628178d7536c715567
parent1379fb052fd18e87a5102e793bdb5b8bc2bf5d17 (diff)
downloadpostgresql-1180b640759b32d63aa95fe8c4a44bec06c65ccb.tar.gz
postgresql-1180b640759b32d63aa95fe8c4a44bec06c65ccb.zip
Make documentation more direct about the handling of COPY files based on
the client encoding.
-rw-r--r--doc/src/sgml/ref/copy.sgml10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index ae6e250e46e..a8e70a581de 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>