Re: citext operator precedence fix

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: citext operator precedence fix
Date: 2011-09-22 16:53:55
Message-ID: 4E7B6823.4000100@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 1. citext_eq(citext,citext)
> 2. citext_eq(text,citext)
> 3. citext_eq(citext,text)
>
> Then the question is: does it find only #2 via polymorphic lookup, or does it think that either #1 or #2 could work (because text supports an implicit cast to citext, IIRC). If it's more than one it's an error. Not sure if the same issue exists for operators.

Well, I just ran through the 7 potential combinations, and didn't get
any errors. Hard to tell which function is being used, of course.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2011-09-22 17:06:00 Re: citext operator precedence fix
Previous Message Martijn van Oosterhout 2011-09-22 16:52:34 Re: EXPLAIN and nfiltered, take two