| From: | Phil Florent <philflorent(at)hotmail(dot)com> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: First draft of PG 19 release notes |
| Date: | 2026-05-01 13:24:51 |
| Message-ID: | FRWPR10MB92546CD6541B46346D890A8FBA322@FRWPR10MB9254.EURPRD10.PROD.OUTLOOK.COM |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I see on many UTF-8 customer bases expression-based index on lower(col) to fulfill some ORM implementation (lower(col) = lower(exp) or "ilike" but ilike is even more "difficult" to index so lower(col) is not so bad...) If pg 19 makes lower(utf-8_text) faster, it's definitely something I would be happy to read in a major upgrade .
Best regards,
Phil
________________________________
De : Andreas Karlsson <andreas(at)proxel(dot)se>
Envoyé : jeudi 30 avril 2026 09:16
À : Bruce Momjian <bruce(at)momjian(dot)us>; PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Objet : Re: First draft of PG 19 release notes
On 4/30/26 9:08 AM, Andreas Karlsson wrote:
> I noticed that two of my performance patches were not included in the
> release notes and I personally think one of them belongs in the release
> notes while other not.
>
> The one I think belongs is the one below since it it really results in
> major speedups of lower(), upper(), initcap() and casefold() on ICU with
> UTF-8. Not having to convert from UTF-8 to UTF-32 and back is often a
> major speedup.
Saw the big discussion on performance improvements if they should be
included or not. So I will just leave this alone. :)
--
Andreas Karlsson
Percona
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2026-05-01 13:46:00 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Etsuro Fujita | 2026-05-01 12:05:57 | Re: Use-after-free issue in postgres_fdw |