Re: Unicode FFFF Special Codepoint should always collate high. - Mailing list pgsql-bugs

From Telford Tendys
Subject Re: Unicode FFFF Special Codepoint should always collate high.
Date
Msg-id 20210623102138.GA18446@mail
Whole thread Raw
In response to Re: Unicode FFFF Special Codepoint should always collate high.  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Unicode FFFF Special Codepoint should always collate high.
List pgsql-bugs
On 21-06-23 18:18, Thomas Munro wrote:
> Just in case you didn't know, PostgreSQL knows how to convert a prefix
> search for 'aar%' into a range search with a related trick in some
> limited circumstances:

Thanks for the suggestion, I probably should learn those tricks but
for the time being, would prefer to live with a slower search and get it
eventually done the way I want.


> Seems a little light on references and justifications for the
> expectiation.  ICU's results could be useful in the discussion.

I trust those guys, they will figure it out. I strongly predict that
they will keep the behaviour consistent with RHEL 7.

Is there an easy way to make normal Linux glibc utilities (e.g. sort)
use a locale from the ICU library? There's a package availble one Centos-8
here:

    libicu-60.3-2.el8_1.x86_64

Trouble is that only a few applications use it, and I can't find any way
to plug-in / plug-out this functionality. Introducing postgresql details to
the bugzilla ticket will muddy the water and create a aura of diffuse
responsibility. What I've found is generally where there's a lot of words,
people don't read them.



pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #17064: Parallel VACUUM operations cause the error "global/pg_filenode.map contains incorrect checksum"
Next
From: Guillaume Lelarge
Date:
Subject: Re: Example in "42.8. Transaction Management" doesn't work for PostgreSQL v 12.7