Horton
Menu

Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed

Rural Hunter <ruralhunter@gmail.com>

View thread
From: Rural Hunter <ruralhunter@gmail.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2012-09-23T14:20:08Z
Lists: 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?

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Replace empty locale name with implied value in CREATE DATABASE and initdb.