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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Gagnon <dgagnon(at)siunik(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
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: 2005-04-06 22:22:02
Message-ID: 6448.1112826122@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

David Gagnon <dgagnon(at)siunik(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mage 2005-04-06 22:26:10 Re: lower function
Previous Message Tom Lane 2005-04-06 22:18:22 Re: monitoring database activity on solaris