Re: plpgsql and index usage - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plpgsql and index usage
Date
Msg-id 486.1040488672@sss.pgh.pa.us
Whole thread Raw
In response to Re: plpgsql and index usage  (Ryan Mahoney <ryan@flowlabs.com>)
List pgsql-hackers
Ryan Mahoney <ryan@flowlabs.com> writes:
>> Hmm ... evidently zipcode is declared as type char(5) (note the "bpchar"
>> coercion).  Is the plpgsql variable it's being compared to declared the
>> same way?  This could be ye olde cross-datatype-coercion problem.

> Interesting!  I think in plpgsql the data type of the argument coming
> in to the function is "text".

Bingo.

>  Are you suggesting that I:
>     a. use a different datatype in plpgsql or 
>     b. cast the values or
>     c. change the data type in the table

Yes ;-).  Presumably (b) would be the least painful route, but any of
these would do the trick.

> I am not familiar with the bpchar type, but I am looking into it now.

Internal name for char(n).
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Michael Paesold"
Date:
Subject: Re: Resource management in 7.4
Next
From: Kenji Sugita
Date:
Subject: How to write make rules for shared library and loadable library