From: Marco Atzeri <marco.atzeri@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Subject: Re: initdb initalization failure for collation "ja_JP"
Date: Wed, 21 Jun 2017 18:43:31 +0200
Message-ID: <3047666b-86e5-1074-0748-b24079d0eee6@gmail.com> (raw)
In-Reply-To: <9154.1497973022@sss.pgh.pa.us>
References: <20c74bc3-d6ca-243d-1bbc-12f17fa4fe9a@gmail.com>
<28708.1497797324@sss.pgh.pa.us>
<9154.1497973022@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 20/06/2017 17:37, Tom Lane wrote:
> I wrote:
>> Marco Atzeri <marco.atzeri@gmail.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" ?
>
> Despite the lack of followup from the OP, I'm pretty troubled by this
> report. It shows that the reimplementation of OS collation data import
> as pg_import_system_collations() is a whole lot more fragile than the
> original coding. We have never before trusted "locale -a" to not produce
> duplicate outputs, not since the very beginning in 414c5a2e. AFAICS,
> the current coding has also lost the protections we added very shortly
> after that in 853c1750f; and it has also lost the admittedly rather
> arbitrary, but at least deterministic, preference order for conflicting
> short aliases that was in the original initdb code.
Hi Tom,
I raised the duplication issue on the cygwin mailing list,
and one of the core developer reports that
they saw the same issues on Linux in the past.
https://cygwin.com/ml/cygwin/2017-06/msg00253.html> regards, tom lane
Regards
Marco
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: marco.atzeri@gmail.com, tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com
Subject: Re: initdb initalization failure for collation "ja_JP"
In-Reply-To: <3047666b-86e5-1074-0748-b24079d0eee6@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox