Re: pgsql: Add option to use ICU as global locale provider - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pgsql: Add option to use ICU as global locale provider
Date
Msg-id 7960418a-b5ac-8a53-bf45-dec2b48e01e9@enterprisedb.com
Whole thread Raw
Responses Re: pgsql: Add option to use ICU as global locale provider  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pgsql: Add option to use ICU as global locale provider  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 18.03.22 10:27, Julien Rouhaud wrote:
> I'm attaching a patch that fixes both issues for me with ICU 50.  Note that
> there's already a test that would have failed for CREATE DATABASE if initdb
> tests didn't fail first, so no new test needed.
> 
> I ended up copy/pasting icu_set_collation_attributes() in initdb.c.  There
> shouldn't be new attributes added in old ICU versions, and there are enough
> differences to make it work in the frontend that it didn't seems worth to have
> a single function.

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.

Why does your patch introduce a function check_icu_locale() that is only 
called once?  Did you have further plans for that?



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Proposal: Support custom authentication methods using hooks
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Add support to table_to_xmlschema regex when timestamp has time zone