From: | Condor <condor(at)stz-bg(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: character encoding |
Date: | 2012-12-06 18:41:44 |
Message-ID: | fe0ca840420b75a6bc8cb5030549eb9d@stz-bg.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2012-12-06 17:30, Adrian Klaver wrote:
> On 12/06/2012 07:20 AM, Doug Kunzman wrote:
>> I'm trying to support an automatic character encoding to UNICODE so
>> Java
>> strings with none ASCII character can be stored in a table.
>>
>> I've edited my postgressql.conf with the following command,
>> PGCLIENTENCODING=UNICODE
>>
>> And I'm getting this error message,
>>
>> FATAL: unrecognized configuration parameter "PGCLIENTENCODING"
>>
>> Any ideas? your help would be appreciated.
>
>
> http://www.postgresql.org/docs/9.2/interactive/runtime-config-client.html#RUNTIME-CONFIG-CLIENT-FORMAT
>
> client_encoding (string)
> Sets the client-side encoding (character set). The default is to
> use the database encoding. The character sets supported by
> the PostgreSQL server are described in Section 22.3.1.
>
> I believe PGCLIENTENCODING is the env setting.
>
>>
>> Thanks, doug
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com
PGCLIENTENCODING is env setting. You can set it before logging in to
database like:
PGCLIENTENCODING=win1251
export PGCLIENTENCODING
and then: psql -U x database
Regards,
Hristo Simeonov
From | Date | Subject | |
---|---|---|---|
Next Message | Emi Lu | 2012-12-06 19:15:29 | Re: Great site for comparing databases (or anything else) |
Previous Message | Glenn Pierce | 2012-12-06 18:31:26 | Re: Trigger / constraint issue |