Thread
-
Re: First draft of PG 19 release notes
Bruce Momjian <bruce@momjian.us> — 2026-05-08T00:52:35Z
On Fri, May 1, 2026 at 01:24:51PM +0000, Phil Florent wrote: > 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 . Yes, agreed. I had not considered how impactful this would be, based on the commit message. Index usage sounds like a huge win. Attached patch applied. --------------------------------------------------------------------------- > Best regards, > Phil > > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ > De : Andreas Karlsson <andreas@proxel.se> > Envoyé : jeudi 30 avril 2026 09:16 > À : Bruce Momjian <bruce@momjian.us>; PostgreSQL-development > <pgsql-hackers@lists.postgresql.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 > > > -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.