Re: PG 18 release notes draft committed - Mailing list pgsql-hackers

From Alexander Borisov
Subject Re: PG 18 release notes draft committed
Date
Msg-id 5984af13-423d-41b0-8081-2f7000cfc5b7@gmail.com
Whole thread Raw
In response to PG 18 release notes draft committed  (Bruce Momjian <bruce@momjian.us>)
Responses Re: PG 18 release notes draft committed
List pgsql-hackers
Hi hackers,

> I will continue improving it until beta 1, and until the final release.
> I will probably add markup in 1-3 weeks.  Let the feedback begin.  ;-)
> 
> You can see the most current HTML-built version here:
> 
>     https://momjian.us/pgsql_docs/release-18.html
> 


I'm not sure, but I'll ask.

I have significantly improved the handling of Unicode Case in
PostgreSQL.
The improvements affect important functions such as lower(), upper(),
casefold().
Specifically, the patch has significantly reduced the size of Unicode
Case tables (and consequently the size of the object file).
We got a significant speed gain:
ASCII by ≈10%
Cyrillic by ≈80%
Unicode in general by ≈30%

But, unfortunately, I didn't see any mention of this improvement in the
release notes.
Hence the question to the community - are such improvements worth
mentioning?

I'm just new to the community, and want to understand.

Commit: 
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=27bdec06841d1bb004ca7627eac97808b08a7ac7

I am now actively working on a major improvement to Unicode
Normalization Forms.

Thanks!


-- 
Regards,
Alexander Borisov




pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: pg_dump to support "on conflict do update"
Next
From: Bruce Momjian
Date:
Subject: Re: PG 18 release notes draft committed