Re: Improve the performance of Unicode Normalization Forms.

Alexander Borisov <lex.borisov@gmail.com>

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

To: Victor Yegorov <vyegorov@gmail.com>

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

Date: 2025-09-11T17:51:45Z

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

> Hey.
> 
> I've looked into these patches.

Hi Victor,

Thank you for reviewing the patch and testing it!

[..]

> Description of the Sparse Array approach is done in the newly introduced
> GenerateSparseArray.pm module.  Perhaps it'd be valuable to add a 
> section into
> the src/common/unicode/README, it'll get more visibility.
> ( Not insisting here. )

It seems that the description of the algorithm that forms the script is
best kept in the script itself.
But I'm not sure either, because I don't know what is customary in the
PG community.


-- 
Regards,
Alexander Borisov