Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed - Mailing list pgsql-hackers

From Rural Hunter
Subject Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Date
Msg-id 505F1A98.9090901@gmail.com
Whole thread Raw
In response to Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
于2012年9月23日 20:33:48,Peter Eisentraut写到:
> On Fri, 2012-09-21 at 17:16 +0800, Rural Hunter wrote:
>> If I run initdb with '-E zh_CN.utf8', it will tell me there
>> is no such charset in the system.
>
> Because that is the name of a locale, not an encoding.
>
>>   I found a workaround to run initdb
>> with '--lc-collate=zh_CN.utf8 --lc-ctype=zh_CN.utf8
>> --lc-messages=zh_CN.utf8 --lc-monetary=zh_CN.utf8
>> --lc-numeric=zh_CN.utf8 --lc-time=zh_CN.utf8'. But the case problem is
>> really confusing.
>
> Try initdb --locale='zn_CN.utf8'.
>
>

Ah yes, seems I used a wrong parameter. The --locale='zh_CN.utf8' 
works. --locale='zh_CN.UTF8' also works. But still the question is, 
should the encoding name be case sensitive?



pgsql-hackers by date:

Previous
From: Euler Taveira
Date:
Subject: Re: [PoC] load balancing in libpq
Next
From: Christopher Browne
Date:
Subject: Re: [PoC] load balancing in libpq