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

Re: initdb of regression test failed.

From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
To: "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: initdb of regression test failed.
Date: 2007-10-03 03:26:04
Message-ID: 08be01c8056d$21262020$c601a8c0@HP22720319231 (view raw, whole thread or download thread mbox)
Lists: pgsql-patches

From: "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>

> "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp> wrote:
>> The database cluster will be initialized with locale Japanese_Japan.932.
>> initdb: locale Japanese_Japan.932 requires unsupported encoding SJIS
>> Encoding SJIS is not allowed as a server-side encoding.
>> -
>> I think that the check of this server side is the right action.!
>> I desire the further suggestion....
> How about changing initdb to use encoding=UTF-8 and no-locale when the
> encoding of default locale is not suppoted in the server? I think it is
> the most frequently used combination when we cannot use the default
> encoding in server.

Yeah, as for Japanese, your suggestion at least is right...I think.
However,  how is it in other countries?  I worry about it...

> The present initdb without options always fails in such environments.
> Using UTF-8 with no-locale is better than error.
> (Error is better than using wrong locale, though.)

Is a method specified and isn't it avoided by the document, rather than 
ad-hoc management? 

Hiroshi Saito

In response to

pgsql-patches by date

Next:From: ITAGAKI TakahiroDate: 2007-10-03 08:28:28
Subject: Re: initdb of regression test failed.
Previous:From: ITAGAKI TakahiroDate: 2007-10-03 03:11:04
Subject: Re: initdb of regression test failed.

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