Re: Optimization of the is_normalized() function.

Alexander Borisov <lex.borisov@gmail.com>

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

To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-10-31T10:42:30Z

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

v2-0001-Optimization-of-the-is_normalized-function.patch (text/plain) patch v2-0001

21.10.2025 19:17, Alexander Borisov wrote:
> Hi, hackers!
> 
> I continue to work on optimizations and improvements in Unicode.
> This patch changes the approach to storing data to determine whether
> a code point is normalized (YES, NO, MAYBE).
> In other words, we are talking about Normalization Quick Check.
Rebase after commit
https://github.com/postgres/postgres/commit/3853a6956c3e3bc7a6fa9bcdb205a2997f46bac2.

--
Best regards,
Alexander Borisov