Re: Seqscan/Indexscan still a known issue?

Guido Neitzer wrote:
> On 27.01.2007, at 00:35, Russell Smith wrote:
>
>> Guess 1 would be that your primary key is int8, but can't be certain
>> that is what's causing the problem.
>
> Why could that be a problem?
Before 8.0, the planner would not choose an index scan if the types were
different int8_col = const, int8_col = 4.
4 in this example is cast to int4.  int8 != int4.  So the planner will
not choose an index scan.

Regards

Russell Smith
>
> cug
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq
>
>