Re: Seqscan/Indexscan still a known issue?

From: Russell Smith <mr-russ(at)pws(dot)com(dot)au>
To: Guido Neitzer <lists(at)event-s(dot)net>
Cc: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Seqscan/Indexscan still a known issue?
Date: 2007-01-27 10:44:10
Message-ID: 45BB2CFA.50609@pws.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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
>
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Scott Marlowe 2007-01-27 11:33:28 Re: Seqscan/Indexscan still a known issue?
Previous Message Tomas Vondra 2007-01-27 09:54:22 Re: Seqscan/Indexscan still a known issue?