Re: pgsql: Add option to use ICU as global locale provider

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add option to use ICU as global locale provider
Date: 2022-03-18 20:04:10
Message-ID: 1221473.1647633850@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2022-03-18 22:09:59 Re: pgsql: Add option to use ICU as global locale provider
Previous Message Tom Lane 2022-03-18 20:02:04 pgsql: Fix incorrect xmlschema output for types timetz and timestamptz.

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-03-18 20:05:32 Re: Proposal: Support custom authentication methods using hooks
Previous Message Tom Lane 2022-03-18 20:02:49 Re: [PATCH] Add support to table_to_xmlschema regex when timestamp has time zone