| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Sandro Santilli <strk(at)kbt(dot)io>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Regina Obe <lr(at)pcorp(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Order changes in PG16 since ICU introduction |
| Date: | 2023-04-21 21:35:09 |
| Message-ID: | 87v8hoexdv.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Jeff" == Jeff Davis <pgsql(at)j-davis(dot)com> writes:
>> Is that the right fix, though? (It forces --locale-provider=libc for
>> the cluster default, which might not be desirable?)
Jeff> For the "no locale" behavior (memcmp()-based) the provider needs
Jeff> to be libc. Do you see an alternative?
Can lc_collate_is_c() be taught to check whether an ICU locale is using
POSIX collation?
There's now another bug in that --no-locale no longer does the same
thing as --locale=C (which is its long-established documented behavior).
How should these various options interact? This all seems not well
thought out from a usability perspective, and I think a proper fix
should involve a bit more serious consideration.
--
Andrew.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2023-04-21 21:56:19 | Re: Order changes in PG16 since ICU introduction |
| Previous Message | Jeff Davis | 2023-04-21 21:25:26 | Re: Order changes in PG16 since ICU introduction |