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

From Julien Rouhaud
Subject Re: pgsql: Add option to use ICU as global locale provider
Date
Msg-id 20220319005914.4qe656mbhh6a44p4@jrouhaud
Whole thread Raw
In response to Re: pgsql: Add option to use ICU as global locale provider  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Mar 18, 2022 at 04:04:10PM -0400, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> 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.

Ok, I also prefer to not have two copies of the code but wasn't sure that
having the error in the boostrapping phase was ok.  I will change that.



pgsql-hackers by date:

Previous
From: "Imseih (AWS), Sami"
Date:
Subject: Re: Allow parallel plan for referential integrity checks?
Next
From: Dean Rasheed
Date:
Subject: Re: [PATCH] Add reloption for views to enable RLS