| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, pg(at)bowt(dot)ie, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Can ICU be used for a database's default sort order? |
| Date: | 2018-12-12 17:53:44 |
| Message-ID: | 75e871c2-bc71-8cf7-7884-bca0eb32ec0c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/12/2018 15:57, Daniel Verite wrote:
> I think one related issue that the patch works around by using a libc locale
> as a proxy is knowing what to put into libc's LC_CTYPE and LC_COLLATE.
> In fact I've been wondering if that's the main reason for the interface
> implemented by the patch.
So it seems, but then it should be called out more clearly.
> Otherwise, how should these env variables be initialized for ICU
> databases?
I think when using ICU by default, then it should not matter because we
shouldn't be calling any libc functions that use those settings. Maybe
there need to be some exceptions, but again we should call those out
more clearly.
We could set them to "C" for consistency perhaps.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-12-12 17:56:53 | Re: Reorganize collation lookup time and place |
| Previous Message | Peter Eisentraut | 2018-12-12 17:48:35 | Re: Reorganize collation lookup time and place |