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 1nVIpg-000551-KF for pgsql-hackers@arkaria.postgresql.org; Fri, 18 Mar 2022 20:04:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nVIpf-0000CN-Ei for pgsql-hackers@arkaria.postgresql.org; Fri, 18 Mar 2022 20:04:19 +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 1nVIpf-0000C6-5y for pgsql-hackers@lists.postgresql.org; Fri, 18 Mar 2022 20:04:19 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nVIpY-0006XT-RZ for pgsql-hackers@lists.postgresql.org; Fri, 18 Mar 2022 20:04:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 22IK4Ato1221474; Fri, 18 Mar 2022 16:04:10 -0400 From: Tom Lane To: Peter Eisentraut cc: Julien Rouhaud , Thomas Munro , Michael Paquier , pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Add option to use ICU as global locale provider In-reply-to: <7960418a-b5ac-8a53-bf45-dec2b48e01e9@enterprisedb.com> References: <20220318031244.tu3wwlyxxabzq3iu@jrouhaud> <20220318063648.4ja6rxlyzvc3viio@jrouhaud> <20220318074051.n46mkwp2zkbxeesf@jrouhaud> <20220318092749.363m4uv6rq24lctz@jrouhaud> <7960418a-b5ac-8a53-bf45-dec2b48e01e9@enterprisedb.com> Comments: In-reply-to Peter Eisentraut message dated "Fri, 18 Mar 2022 20:28:58 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1221472.1647633850.1@sss.pgh.pa.us> Date: Fri, 18 Mar 2022 16:04:10 -0400 Message-ID: <1221473.1647633850@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Peter Eisentraut writes: > Another option is that we just don't do the check in initdb. As the > tests show, you will then get an error from the backend call, so it's > really just a question of when the error is reported. +1 ... seems better to not have two copies of the code. regards, tom lane