Received: from makus.postgresql.org ([98.129.198.125])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ruralhunter@gmail.com>) id 1TFn2y-0006qt-9O
	for pgsql-hackers@postgresql.org; Sun, 23 Sep 2012 14:20:36 +0000
Received: from mail-pb0-f46.google.com ([209.85.160.46])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <ruralhunter@gmail.com>) id 1TFn2v-0000J8-Of
	for pgsql-hackers@postgresql.org; Sun, 23 Sep 2012 14:20:35 +0000
Received: by pbbrr4 with SMTP id rr4so5668440pbb.19
	for <pgsql-hackers@postgresql.org>;
	Sun, 23 Sep 2012 07:20:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	bh=cBLLCYfW1t85vfNSuaYJQKP6X1wvkrZU0SzEeqXVaDY=;
	b=zRD6L/PRReePBXTvS+q80oKCp1cK4welROt5Yvju8c3Uh4Pi2LyB0sGknJZ36Ys8i2
	8o/3l+kSUAs2xdW435u/PaBy3u2ixaEGuqiZsmy6iLKRv7U97Nf/fu1L1TT/bGIfH65g
	150/kltLeH7RKaUbt0dzO60IvVuXGEtDC2w9HrfMgaNjoDKX69Lkp7SDlb2nh6X7O4dt
	j9lOovOdtJY849Sx4AOGDJwO8LsuodFy151OW0cjO3hb/iQjDi63j4fSMxo4B1kcicYC
	J2qDVID4wcOm63DOui4KRyzhXQiq6vox56wzpHatveMmhex2iXCeR8ZgpCqylad/7Pf1
	rE4g==
Received: by 10.66.73.9 with SMTP id h9mr26032477pav.76.1348410032460;
	Sun, 23 Sep 2012 07:20:32 -0700 (PDT)
Received: from [192.168.11.3] ([114.95.126.189])
	by mx.google.com with ESMTPS id ih2sm8123902pbc.65.2012.09.23.07.20.21
	(version=TLSv1/SSLv3 cipher=OTHER);
	Sun, 23 Sep 2012 07:20:30 -0700 (PDT)
Message-ID: <505F1A98.9090901@gmail.com>
Date: Sun, 23 Sep 2012 22:20:08 +0800
From: Rural Hunter <ruralhunter@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
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>
Subject: Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
References: <50535302.8080000@gmail.com> <20120914183915.GA5933@momjian.us>
	<5053F896.60005@gmail.com> <20120915180603.GA20907@momjian.us>
	<505557CD.8090304@gmail.com> <20120916171746.GA24907@momjian.us>
	<28666.1347833056@sss.pgh.pa.us>
	<20120917043236.GA20123@momjian.us> <5056AF29.3040903@gmail.com>
	<20120917210723.GA30394@momjian.us>
	<20120918232239.GA2014@momjian.us> <505C307E.20501@gmail.com>
	<1348403628.18490.1.camel@vanquo.pezone.net>
In-Reply-To: <1348403628.18490.1.camel@vanquo.pezone.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Pg-Spam-Score: -2.6 (--)
X-Archive-Number: 201209/841
X-Sequence-Number: 213869

于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?