Mitch Skinner <[EMAIL PROTECTED]> writes:
> This is with Postgres 8.0.3.  Any advice is appreciated.

These are exactly the same plan, except for the addition of the extra
filter condition ...

>    ->  Index Scan using external_id_map_primary_key on external_id_map
> eim  (cost=0.00..2345747.01 rows=15560708 width=26) (actual
> time=0.061..2.944 rows=2175 loops=1)

>    ->  Index Scan using external_id_map_primary_key on external_id_map
> eim  (cost=0.00..2384648.78 rows=4150 width=26) (actual
> time=0.020..21068.508 rows=1186 loops=1)
>          Filter: (source = 'SCH'::bpchar)

Apparently, you are using a platform and/or locale in which strcoll() is
spectacularly, god-awfully slow --- on the order of 10 msec per comparison.
This is a bit hard to believe but I can't make sense of those numbers
any other way.  What is the platform exactly, and what database locale
and encoding are you using?

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

Reply via email to