Skip site navigation (1) Skip section navigation (2)

Re: Next: Encoding Issue

From: Devin Ben-Hur <devin(at)ben-hur(dot)net>
To: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
Cc: "Ewan, Michael" <michael(dot)ewan(at)intel(dot)com>, "pdxpug(at)postgresql(dot)org" <pdxpug(at)postgresql(dot)org>
Subject: Re: Next: Encoding Issue
Date: 2009-02-03 05:40:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pdxpug
Ewan, Michael wrote:
> In the shell environment
> export LC_ALL=C
> This will often fix many locale ills.

You will likely want to reinitialize your database cluster with `initdb 
--locale=C --encoding=UTF-8 -D /where/ever/your/database/is`.  Once the 
locale for a cluster is set, it can not be changed (though alternate 
compatible encodings can be specified per database) and it looks like 
the Rich's was init'd with locale=en_US.LATIN1 which will not 
accommodate a UTF8 encoding.

>> -----Original Message-----
>>   I'm seeing this error when I try to create a database
>> within TinyERP:
>> createdb: database creation failed: ERROR:  encoding UTF8 does
>> not match
>> server's locale en_US
>> DETAIL:  The server's LC_CTYPE setting requires encoding LATIN1.
>>   The application is designed for unicode (that's UTF8, isn't
>> it?) and I
>> cannot pass the '-E' option to the createdb command within the
>> application.
>> Please suggest approaches to resolve this conflict.

In response to


pdxpug by date

Next:From: Ewan, MichaelDate: 2009-02-03 06:01:38
Subject: Re: Dropping Old Databases
Previous:From: Ewan, MichaelDate: 2009-02-03 04:52:28
Subject: Re: Next: Encoding Issue

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group