Re: BUG #16333: position() function not equivalent to strpos()function when comparing citext - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #16333: position() function not equivalent to strpos()function when comparing citext
Date
Msg-id d86632ce-76fe-5a3e-abd1-f739b0e3e204@2ndquadrant.com
Whole thread Raw
In response to Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 2020-04-02 23:46, Tom Lane wrote:
>> Doesn't seem fixable.  Collations are probably a better way of dealing
>> with this.
> 
> Yeah, now that we can do non-deterministic collations, it seems like
> citext is on the road to obsolescence.  Do we have a documentation
> example of how to build a simple CI collation?

Yes, in PG12 there is a "tip" box in the citext chapter with a link to 
the collation documentation which contains a command to create a 
case-insensitive collation.  So this should be pretty easy to find even 
for casual users.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16343: Build problem: Install.pm "Could not find debug or release binaries"
Next
From: Peter Eisentraut
Date:
Subject: Re: BUG #16342: CREATE TABLE LIKE INCLUDING GENERATED column orderissue