Re: planner doesn't use multicolumn index - Mailing list pgsql-performance

From Tomasz Myrta
Subject Re: planner doesn't use multicolumn index
Date
Msg-id 3F841CAF.6070202@klaster.net
Whole thread Raw
In response to planner doesn't use multicolumn index  (Adrian Demaestri <ademaestri@yahoo.com>)
List pgsql-performance
> We've a table with about 8 million rows, and we need to get rows by the
> value of two of its fields( the type of the fields are int2 and int4,
> the where condition is v.g. partido=99 and partida=123). We created a
> multicolumn index on that fields but the planner doesn't use it, it
> still use a seqscan. That fields are primary key of the table and we
> clusterded the table based on that index, but it still doesn't work. We
> also set the enviroment variable enable_seqscan to false and nathing
> happends. The only way the planner use it is in querys that order by the
> expression of the index.
> Any idea?
> thanks.
> Adrián

where partido=99::int2 and partida=123;

Regards,
Tomasz Myrta


pgsql-performance by date:

Previous
From: Adrian Demaestri
Date:
Subject: planner doesn't use multicolumn index
Next
From: Shridhar Daithankar
Date:
Subject: Re: planner doesn't use multicolumn index