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

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add option to use ICU as global locale provider
Date: 2022-03-18 19:30:21
Message-ID: 9cbb672e-a33f-3102-4aaf-758495f7a237@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 18.03.22 18:29, Tom Lane wrote:
> I found a different problem with src/test/icu/: it fails altogether
> if the prevailing locale is "C", because then the database encoding
> defaults to SQL_ASCII which our ICU code won't cope with. I'm not
> sure if that explains any of the buildfarm failures, but it broke
> my local build (yeah, I'm that guy). I un-broke it for the moment
> by forcing the test to use UTF8 encoding, but do we want to do
> anything smarter than that?

This is an appropriate solution, I think.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-03-18 20:02:04 pgsql: Fix incorrect xmlschema output for types timetz and timestamptz.
Previous Message Peter Eisentraut 2022-03-18 19:28:58 Re: pgsql: Add option to use ICU as global locale provider

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-03-18 20:02:49 Re: [PATCH] Add support to table_to_xmlschema regex when timestamp has time zone
Previous Message Peter Eisentraut 2022-03-18 19:28:58 Re: pgsql: Add option to use ICU as global locale provider