pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: me@reynolds.tj
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext
Date: Thu, 2 Apr 2020 22:53:17 +0200
Message-ID: <9817af55-fbe4-b342-b641-637f1308ef96@2ndquadrant.com> (raw)
In-Reply-To: <12376.1585789484@sss.pgh.pa.us>
References: <16333-dd25eea9d90e244d@postgresql.org>
	<12376.1585789484@sss.pgh.pa.us>

On 2020-04-02 03:04, Tom Lane wrote:
> PG Bug reporting form <noreply@postgresql.org> writes:
>> SELECT position('foo'::citext IN 'Foobar'::citext) =
>> strpos('Foobar'::citext, 'foo'::citext) as "positionEqualsStrpos";
> 
>> Citext does not create an overload for position() supporting citext
>> parameters, therefore position(a in b) always runs case-sensitive.
> 
> Well, the citext documentation specifies which functions have
> case-insensitive mappings.  strpos() is listed, position() is not,
> so I'd say it's acting precisely as documented.

Arguably, there is a misdesign here, however.  Any function that does 
some kind of text-in-text search where citext could plausbily offer 
case-insensitive behavior will automatically fall back to the 
case-sensitive version if citext doesn't offer its own variant.  The fix 
would technically need to be that citext offers its own variant of every 
potential such function, which is clearly not possible, or that casts 
between text and citext are more restricted, which would make citext 
nearly unusable.

Doesn't seem fixable.  Collations are probably a better way of dealing 
with this.

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





view thread (6+ messages)  latest in thread

Message-ID: <9817af55-fbe4-b342-b641-637f1308ef96@2ndquadrant.com>
Permalink:  ../9817af55-fbe4-b342-b641-637f1308ef96@2ndquadrant.com/
Also on:    postgresql.org/message-id/9817af55-fbe4-b342-b641-637f1308ef96@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, me@reynolds.tj
  Subject: Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext
  In-Reply-To: <9817af55-fbe4-b342-b641-637f1308ef96@2ndquadrant.com>
  References: <16333-dd25eea9d90e244d@postgresql.org> <12376.1585789484@sss.pgh.pa.us> <9817af55-fbe4-b342-b641-637f1308ef96@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox