From: Russell Smith <mr-russ@pws.com.au>
To: Guido Neitzer <lists@event-s.net>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Seqscan/Indexscan still a known issue?
Date: Sat, 27 Jan 2007 21:44:10 +1100
Message-ID: <45BB2CFA.50609@pws.com.au> (raw)
In-Reply-To: <58F562A7-2925-4E37-BEA7-3D26748D408A@event-s.net>
References: <45BAB682.6060709@mochima.com>
<45BB00BB.4070009@pws.com.au>
<58F562A7-2925-4E37-BEA7-3D26748D408A@event-s.net>
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
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mr-russ@pws.com.au, lists@event-s.net
Subject: Re: Seqscan/Indexscan still a known issue?
In-Reply-To: <45BB2CFA.50609@pws.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox