| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: fixing tsearch locale support |
| Date: | 2024-12-17 18:27:07 |
| Message-ID: | 4bbdfe2d-f6c6-491e-90fb-4c5604321b9a@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17.12.24 16:25, Andreas Karlsson wrote:
> On 12/13/24 6:07 PM, Jeff Davis wrote:
>> OK, that's fine with me for this patch series.
>>
>> Eventually though, I think we should have built-in versions of these
>> ASCII functions. Even if there's no actual problem, it would more
>> clearly indicate that we only care about ASCII at that particular call
>> site, and eliminate questions about what libc might do on some platform
>> for some encoding/locale combination. It would also make it easier to
>> search for locale-sensitive functions in the codebase.
>
> +1 I had exactly the same idea.
Yes, I think that could make sense.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-12-17 18:27:12 | Re: improve EXPLAIN for wide tables |
| Previous Message | Jeff Davis | 2024-12-17 18:10:50 | Re: Remaining dependency on setlocale() |