Re: Optimizer is not choosing index

Hi Tom,

thanks for your suggestion:

> Markus Innerebner <markus(dot)innerebner(at)inf(dot)unibz(dot)it> writes:
>> The query plan says, that a sequential scan is performed on the edge table. I consider it strange that he is not accessing on the (btree) index one the edge table.
>
> This suggests that you have a datatype mismatch:
>
>> " Hash Cond: ((e.target)::numeric = n.id)"
>
> Your index is presumably on e.target, not e.target::numeric, so it's not
> applicable. Try to make the join columns the same datatype.

indeed: the id column in the node table had as type numeric, while in edges the target is integer.

After changing it, the index is used again.

many thanks

cheers Markus