Postgres Pro
Downloads
Home   >   mailing lists

Re: COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion - Mailing list pgsql-general

From Tom Lane
Subject Re: COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion
Date
Msg-id 6448.1112826122@sss.pgh.pa.us
Whole thread Raw
In response to COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion  (David Gagnon <dgagnon@siunik.com>)
Responses Re: COPY command use UTF-8 encoding and NOT UNICODE(16bits)... please confirm. Should postgresql add :set CLIENT_ENCODING to 'UTF-8'; to avoid confusion
List pgsql-general
Tree view 
David Gagnon <dgagnon@siunik.com> writes:
> So am I right ? Is Postgresql using UTF-8 and don`t really understand
> UNICODE file (UCS-2)?  Is there a way I can make the COPY command with a
> UNICODE UCS-2 encoding

Postgres only supports UTF-8, not any other encoding of Unicode.  Sorry.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: monitoring database activity on solaris
Next
From: Mage
Date:
Subject: Re: lower function