Re: Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)
Date
Msg-id 4012.1008346014@sss.pgh.pa.us
Whole thread Raw
In response to Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)  (Nicolai@ISYS.DK)
Responses Re: Unable to compare _bpchar for similarity in WHERE-clause  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Unable to compare _bpchar for similarity in WHERE-clause (MINOR A NNOYANCE)  (Justin <aa2@bigpond.net.au>)
List pgsql-bugs
Nicolai@ISYS.DK writes:
> When I try to write an UPDATE where I include a WHERE-clause like:
> [WHERE something='{"a","b","c"}], where something is a character[], i get
> the errormessage:[Unable to identify an operator = for types '_bpchar and
> 'unknown' You will have to retype this query using an explicit cast]
> The above statement works for text[].

Hmm.  Looks like there is a pg_operator entry for text[] = text[],
but none for bpchar[] = bpchar[].  This is an oversight, nothing more.
Feel free to add such an entry --- it can point to the same array-equals
function as the one for text[].

It's too late to fix this in the standard catalogs for 7.2, but I'll
make a note for 7.3.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Bug #539: Unexpected DeadLock on REFERENCES
Next
From: Markus Bertheau
Date:
Subject: stuck spinlock. Aborting. What does this mean?