Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: me(at)reynolds(dot)tj, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext
Date: 2020-04-05 10:41:51
Message-ID: d86632ce-76fe-5a3e-abd1-f739b0e3e204@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2020-04-05 11:28:20 Re: BUG #16342: CREATE TABLE LIKE INCLUDING GENERATED column order issue
Previous Message PG Bug reporting form 2020-04-04 15:08:31 BUG #16343: Build problem: Install.pm "Could not find debug or release binaries"