Re: Order changes in PG16 since ICU introduction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
Cc: "Jeff Davis" <pgsql(at)j-davis(dot)com>, Regina Obe <lr(at)pcorp(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Sandro Santilli <strk(at)kbt(dot)io>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Order changes in PG16 since ICU introduction
Date: 2023-04-25 15:20:38
Message-ID: 691392.1682436038@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Daniel Verite" <daniel(at)manitou-mail(dot)org> writes:
> FTR the full text search parser still uses the libc functions
> is[w]space/alpha/digit... that depend on lc_ctype, whether the db
> collation provider is ICU or not.

Yeah, those aren't even connected up to the collation-selection
mechanisms; lots of work to do there. I wonder if they could be
made to use regc_pg_locale.c instead of duplicating logic.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2023-04-25 15:32:47 Re: enhancing plpgsql debug api - hooks on statements errors and function errors
Previous Message Masahiko Sawada 2023-04-25 15:02:25 Re: Should vacuum process config file reload more often