Re: Improve the performance of Unicode Normalization Forms.

Alexander Borisov <lex.borisov@gmail.com>

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

To: Jeff Davis <pgsql@j-davis.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2025-07-08T19:42:20Z

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 →

Use C11 char16_t and char32_t for Unicode code points.
- 3853a6956c3e 19 (unreleased) cited

Attachments

v3-0001-Moving-Perl-functions-Range-index-to-a-common-mod.patch (text/plain) patch v3-0001
v3-0002-Improve-the-performance-of-Unicode-Normalization-.patch (text/plain) patch v3-0002

07.07.2025 21:44, Alexander Borisov пишет:
> 30.06.2025 22:28, Jeff Davis пишет:
>> On Tue, 2025-06-24 at 18:20 +0300, Alexander Borisov wrote:
>>> That's what we're aiming for - to implement the fastest approach.
>>
>> Awesome! Thank you for clarifying this as a goal. Having the fastest
>> open-source Unicode normalization would be a great thing to highlight
>> when this is done.
> 
> After the discussion in this correspondence, we are settling on
> the "small" patch option. The table size is reduced, the speed is
> almost x2.
> Attached are the final two patches. After reviewing/accepting them,
> I will proceed to optimizing the C code for Unicode Normalization Forms.

Version 3 patches. In version 2 "make -s headerscheck" did not work.

--
Regards,
Alexander Borisov