| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Alexander Borisov <lex(dot)borisov(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Optimization for lower(), upper(), casefold() functions. |
| Date: | 2025-02-12 18:56:51 |
| Message-ID: | 78ea431838fca358bc13c6fbe96cfae535d413f1.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2025-02-11 at 23:08 +0300, Alexander Borisov wrote:
> What's the result?
>
> I would use Range Binary in Unicode case/normalization. The algorithm
> shows good results. Plus it can be customized (increasing/decreasing)
> the table by allowing empty values.
>
> Also, I got a strong feeling that Encoding could be optimized and
> improved. I am interested in this direction and would try my hand at
> improving Encodings.
>
> But I can't grab it all at once, it takes a systematic approach.
> I suggest starting with Unicode Case, then Unicode Normalization.
> Then experiment and improve Encoding.
Thank you.
That sounds good to me, I'll start looking at the patch details.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-02-12 19:01:15 | Re: pg_stat_statements and "IN" conditions |
| Previous Message | Dagfinn Ilmari Mannsåker | 2025-02-12 18:49:52 | Re: Small memory fixes for pg_createsubcriber |