Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dNijg-0001HA-6y for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Jun 2017 16:44:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dNijf-0005vv-EO for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Jun 2017 16:44:07 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dNijd-0005uQ-Ua for pgsql-hackers@postgresql.org; Wed, 21 Jun 2017 16:44:06 +0000 Received: from mail-wr0-x241.google.com ([2a00:1450:400c:c0c::241]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dNija-000301-P9 for pgsql-hackers@postgresql.org; Wed, 21 Jun 2017 16:44:04 +0000 Received: by mail-wr0-x241.google.com with SMTP id x23so27941354wrb.0 for ; Wed, 21 Jun 2017 09:44:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=LD9zhxOjNTa+qfbwnbhYM4XYeglW4qpeY/qNbQxpRLA=; b=DjIfv+MDf07I1rHRXhaPxrtbXK31qAePuNykhoUZf5adhaq5VNDKEfls+T/Nm6ziYV mBWmRg4fmqUVsQJKFalFCC+6n8V8gfGA1W9vBiVe0A0+8uLGHHh3+tY+51gE8RoGJIC3 bioX+MEA3KUrZZQq1a8ojInOVEgiQOarv7jIxnhs1yU5+9lSgv0kPHEhN9Bf2IaCEKeG XCC+UMdL+ohFisz1Ex2jUlYoO0pJhuDLmgbWoBqI51l0Fd6aJdf89PWN/MjJQ4Rs2AfX AKQTZvYu+eMD4LRjP0IW3hBXGNcUP6oMpcqfz7o2lUZTsbVFmOewEq4cOVVeJhb1fYyV HKlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=LD9zhxOjNTa+qfbwnbhYM4XYeglW4qpeY/qNbQxpRLA=; b=dKo9FqwPsvQyTC9KEW9wv8cUbp1bXdwrl+M00rjTqZcFqqDr4d5P61VCDaY3urQJDG ENJ0/d/tI/57Katu9y13nFzOxbzQmGIyHnOnR2j7J6XQDHUu3ICYGe66DVetfzGrLULi umkPQdsFkErzgfIs49JZEUC7X7ORvNx5Dr+fWXNt39SIck628BV7ng/F3EFCed08nxQ1 m7Zxj7Wk7eFZGJWxH4cUywUvTIhcQIw/2kqkPHsrVRKjV1RdBO7sI5ZPYFmxfU1SmTCS 7nybz3Z/Z0j2Q8U1dwuU9XGsJ+tzbz/hnRhfEzFT1oys8TfqcGow5b/ZumwAPgb5dDuv mTFw== X-Gm-Message-State: AKS2vOyyEAK8lH1NQQvAK2NjNhKLhhqqCzf44J51S1z9Jj3M9XcE49U/ HY+mky3sS+CDFz4l40s= X-Received: by 10.28.129.149 with SMTP id c143mr7157326wmd.47.1498063440511; Wed, 21 Jun 2017 09:44:00 -0700 (PDT) Received: from [192.168.138.68] ([62.154.173.198]) by smtp.googlemail.com with ESMTPSA id e130sm22613802wmf.10.2017.06.21.09.43.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Jun 2017 09:43:59 -0700 (PDT) Subject: Re: initdb initalization failure for collation "ja_JP" To: Tom Lane , Peter Eisentraut References: <20c74bc3-d6ca-243d-1bbc-12f17fa4fe9a@gmail.com> <28708.1497797324@sss.pgh.pa.us> <9154.1497973022@sss.pgh.pa.us> Cc: PostgreSQL mailing lists From: Marco Atzeri Message-ID: <3047666b-86e5-1074-0748-b24079d0eee6@gmail.com> Date: Wed, 21 Jun 2017 18:43:31 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <9154.1497973022@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 20/06/2017 17:37, Tom Lane wrote: > I wrote: >> Marco Atzeri 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