Re: Optimization for lower(), upper(), casefold() functions.

Alexander Borisov <lex.borisov@gmail.com>

From: Alexander Borisov <lex.borisov@gmail.com>

To: Jeff Davis <pgsql@j-davis.com>, Heikki Linnakangas <hlinnaka@iki.fi>, pgsql-hackers@postgresql.org

Date: 2025-03-02T20:33:07Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix headerscheck warning.
- 549ea06e4217 18.0 landed
Optimization for lower(), upper(), casefold() functions.
- 27bdec06841d 18.0 landed
Refactor convert_case() to prepare for optimizations.
- d3b2e5e1ab5c 18.0 landed
Improve performance of Unicode {de,re}composition in the backend
- 783f0cc64dcc 14.0 cited

19.02.2025 01:56, Jeff Davis пишет:
> On Wed, 2025-02-19 at 01:54 +0300, Alexander Borisov wrote:
>> In proposing the patch for v3, I struck a balance between improving
>> performance and reducing binary size, without sacrificing code
>> clarity.
> 
> Fair enough. I will continue reviewing v3.

Did you have a time for review this?

I'd like to continue improving Unicode in Postgres, as I previously
wrote, next in my plans are Normalization forms, and more.
But now I am blocked by this patch.

--
Alexander Borisov