Hi. From: "Tom Lane" <[EMAIL PROTECTED]>
"Hiroshi Saito" <[EMAIL PROTECTED]> writes:The database cluster will be initialized with locale Japanese_Japan.932. initdb: could not find suitable encoding for locale "Japanese_Japan.932"So, what encoding *should* we use for that locale?I think this is required....We are certainly not going to disable pg_regress's ability to test in non-C locales. ISTM a proper fix is an addition to the table in src/port/chklocale.c. This example suggests actually that we need a boatload more table entries to handle Windows locale names :-( (count on Microsoft to ignore standards...)
Ah Ok, Please check it. However, This problem.... - Running in noclean mode. Mistakes will not be cleaned up.^M The files belonging to this database system will be owned by user "hiroshi".^M This user must also own the server process.^M ^M The database cluster will be initialized with locale Japanese_Japan.932.^M initdb: locale Japanese_Japan.932 requires unsupported encoding SJIS^M Encoding SJIS is not allowed as a server-side encoding.^M Rerun initdb with a different locale selection.^M Running in noclean mode. Mistakes will not be cleaned up.^M - I think that the check of this server side is the right action.! I desire the further suggestion.... Regards, Hiroshi Saito
chklocale_patch
Description: Binary data
---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
