Re: initdb initalization failure for collation "ja_JP"

From: Marco Atzeri <marco(dot)atzeri(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: initdb initalization failure for collation "ja_JP"
Date: 2017-06-20 20:34:11
Message-ID: 37298718-39fa-ed44-89fb-b83987084531@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18/06/2017 16:48, Tom Lane wrote:
> Marco Atzeri <marco(dot)atzeri(at)gmail(dot)com> writes:
>> Building on Cygwin latest 10 beta1 or head sourece,
>> make check fails as:
>> ...
>> performing post-bootstrap initialization ... 2017-05-31 23:23:22.214
>> CEST [16860] FATAL: collation "ja_JP" for encoding "EUC_JP" already exists
>
> Hmph. Could we see the results of "locale -a | grep ja_JP" ?
>
> regards, tom lane
>

$ locale -a |grep -i ja
ja_JP
ja_JP
ja_JP.utf8
ja_JP.ujis
ja_JP(at)cjknarrow
ja_JP(dot)utf8(at)cjknarrow
japanese
japanese.euc
japanese.sjis

$ locale -a |grep -i "euc"
japanese.euc
korean.euc

Regards
Marco

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-06-20 20:35:36 Re: Typo in insert.sgml
Previous Message Tom Lane 2017-06-20 20:19:13 Re-indent HEAD tomorrow?