Re: plpgsql and index usage

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ryan Mahoney <ryan(at)flowlabs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: plpgsql and index usage
Date: 2002-12-20 23:27:49
Message-ID: 25782.1040426869@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ryan Mahoney <ryan(at)flowlabs(dot)com> writes:
> Index Scan using pa_zipcode_proximity_pk on pa_zipcode_proximity (cost=
> 0.00..13.53 rows=3 width=862)
> Index Cond: ((zipcode = '11103'::bpchar) AND (proximity <= 100))
> (183 rows)

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2002-12-21 02:29:44 Resource management in 7.4
Previous Message Ryan Mahoney 2002-12-20 22:35:19 plpgsql and index usage