Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o8A2d-0002Sp-7g for pgsql-bugs@arkaria.postgresql.org; Mon, 04 Jul 2022 00:34:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o8A2b-00057c-6s for pgsql-bugs@arkaria.postgresql.org; Mon, 04 Jul 2022 00:34:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o8A2a-0004yf-Su for pgsql-bugs@lists.postgresql.org; Mon, 04 Jul 2022 00:34:16 +0000 Received: from mail-pf1-x434.google.com ([2607:f8b0:4864:20::434]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o8A2U-0006Hi-5D for pgsql-bugs@lists.postgresql.org; Mon, 04 Jul 2022 00:34:15 +0000 Received: by mail-pf1-x434.google.com with SMTP id x4so7571819pfq.2 for ; Sun, 03 Jul 2022 17:34:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:message-id:to:cc:subject:from:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=1Cdo8XVnMXA6oDgqZ3Qlk86yyufEhTfLTu8fpg4AH6k=; b=hmavaMOH9zmAgt2CsGv5AA0fSa+ky0pNGtNP2GhbTLJpVY3aHB5bJUw7yxRUL06Y1/ sND9Ry0CXP3KQvLDOWZwoMAsBhCVHvEHEWQMA7FQG6ShPonxLO2r+JT9CjuFDh2u0BF0 /ajzSIU2RSBVtxkpcvNlgMokn/qfleUzFisxKnae3Wght4eTzKydS3h7awNKrWyxiZSl 05u46rdJTFCOU1wwqQOuCjoR5ejPeBcuqWJDgPGohL5jZja7SPyMUeuxbmZp1BvEX9UT ICExfIilmlY2KL7nMm9bqArjCJqY9lIj6RjctUvbKjvyLYSbDe4aYCJSKCrT9xXsA9z/ N7DQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:message-id:to:cc:subject:from:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=1Cdo8XVnMXA6oDgqZ3Qlk86yyufEhTfLTu8fpg4AH6k=; b=JDmZDlkrsZ4pNtraXVc6Ug//IjqE8iB5oKpoCqC8xKG8OgnF//i4JgVIstz8vfNcT1 yjvPuchxbgyCTDU5icrfSvdTtV32fmFSGFuTa/1Enc6oCNXNGDVLEXtdxC9l07pLJhiP tguzb4odH2qm2xF7L3aCRcmKBhZ1KO3VTnREs7Fy337Tb0Pq7PvV7hW2aD3ZjzgNxmY1 Zw9muDMOtjvCSfAc1hjXj82qGwNkqw57MotM4FU1K0/WxVdXOlUXgmUtHQgZw3SrMC3O 8wkAqy8i5qIFIeka3TvpSx/uNjWpklKzZxM20dcAUD1wg9/H3HTb6RPggjW0DRYWJvyd x9sQ== X-Gm-Message-State: AJIora9ZUrgnQBlmQc5DRS4B1dAibcC9jD7QsyDWzyUOOM/ASNkxqnZ9 teIYbVFSghVRGLb5FmmISmM= X-Google-Smtp-Source: AGRyM1sQUdxw3t6+c1XEZJ2Cl3EOUr+STanZAdXMymRmXTgVRP9VP8h2GrUzzGwXQnujqG8ncGovuA== X-Received: by 2002:a63:2b8c:0:b0:411:954c:1f1f with SMTP id r134-20020a632b8c000000b00411954c1f1fmr19548819pgr.548.1656894849108; Sun, 03 Jul 2022 17:34:09 -0700 (PDT) Received: from localhost (KD036014041111.ppp-bb.dion.ne.jp. [36.14.41.111]) by smtp.gmail.com with ESMTPSA id k13-20020a635a4d000000b0041173d92b35sm9789260pgm.81.2022.07.03.17.34.06 (version=TLS1_3 cipher=TLS_CHACHA20_POLY1305_SHA256 bits=256/256); Sun, 03 Jul 2022 17:34:07 -0700 (PDT) Date: Mon, 04 Jul 2022 09:34:05 +0900 (JST) Message-Id: <20220704.093405.1243358043142197360.horikyota.ntt@gmail.com> To: sh@rosesoft.de Cc: pgsql-bugs@lists.postgresql.org Subject: Re: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012 From: Kyotaro Horiguchi In-Reply-To: <62310c8c50c74861b80d908310f8a880@rosesoft.de> References: <62310c8c50c74861b80d908310f8a880@rosesoft.de> User-Agent: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk At Fri, 1 Jul 2022 13:07:13 +0000, "ROSESOFT S. Hoffmann" wrote in = > initdb.exe .. -E UTF8 --locale=3Dde-x-icu --text-search-config=3Dgerm= an .. > = > Error message: > initdb: ung=FCltiger Locale-Name =BBde-x-icu=AB > According to https://www.postgresql.org/download/windows/ PostgreSQL > 10 is supported by Windows Server 2012. If you are unfortunately using PostgreSQL 10, it doesn't support ICU collations as the default for databases. It's a new feature of 15. https://www.postgresql.org/docs/15/release-15.html > - Allow ICU collations to be set as the default for clusters and > databases (Peter Eisentraut) > Previously, ICU collations could only be specified in CREATE > COLLATION and used with the COLLATE clause. If you are using PG15, --icu-locale accompanied by --locale-provider=3Dicu instead of --locale will work for you. https://www.postgresql.org/docs/devel/app-initdb.html > Alternatively, the ICU library can be used to provide locale > services. (Again, this only sets the default for subsequently created= > databases.) To select this option, specify --locale-provider=3Dicu. T= o > choose the specific ICU locale ID to apply, use the option > --icu-locale. Note that for implementation reasons and to support > legacy code, initdb will still select and initialize libc locale > settings when the ICU locale provider is used. regards. -- = Kyotaro Horiguchi NTT Open Source Software Center