Skip site navigation (1) Skip section navigation (2)

Re: Inefficient query plan

From: Jann Röder <roederja(at)ethz(dot)ch>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Inefficient query plan
Date: 2010-08-23 10:20:02
Message-ID: i4ti0i$hec$1@dough.gmane.org (view raw or flat)
Thread:
Lists: pgsql-performance
Am 23.08.10 12:18, schrieb Scott Marlowe:
> On Mon, Aug 23, 2010 at 4:15 AM, Jann Röder <roederja(at)ethz(dot)ch> wrote:
>> Am 23.08.10 07:52, schrieb Scott Marlowe:
>>> Also are a.indexid and b.indexid the same type?
>>>
>>
>> You mean ItemID? Fields of the same name are of the same type - so yes.
>> According to the documentation pgsql adds indexes for primary keys
>> automatically so (b.itemID, b.indexNumber) is indexed. Or do you think
>> adding an extra idnex for b.itemID alone will help? If I understand the
>> documentation correctly, pqSQL can use the first column of a
>> multi-column index as if it was indexed individually... but maybe I'm
>> wrong here.
> 
> It can but that doesn't mean it will.  A multi-column index is often
> quite a bit bigger than a single column one.
> 
> What happens if you try
> 
> set enable_seqscan=off;
> (your query here)
> 
Tried that already. The query plan is exactly the same.


In response to

pgsql-performance by date

Next:From: Kevin GrittnerDate: 2010-08-23 12:08:22
Subject: Re: Inefficient query plan
Previous:From: Scott MarloweDate: 2010-08-23 10:18:02
Subject: Re: Inefficient query plan

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group