On Monday 12 January 2009, "Scott Marlowe" wrote:
> I've found that when you do frequently query on two or more columns, a
> multi-column index is faster than bitmap scans, especially for larger
> data sets.
Very much faster, especially if you're only looking for a few dozen or
hundred rows out
On Mon, Jan 12, 2009 at 12:23 PM, Andreas Kretschmer
wrote:
> Jörg Kiegeland schrieb:
>
>> Hello,
>>
>> I created a multicolumn index on the columns c_1,..,c_n .
>> If I do use only a true subset of these columns in a SQL query, is the
>> index still efficient?
>> Or is it better to create anothe
Jörg Kiegeland schrieb:
> Hello,
>
> I created a multicolumn index on the columns c_1,..,c_n .
> If I do use only a true subset of these columns in a SQL query, is the
> index still efficient?
> Or is it better to create another multicolumn index defined on this subset?
Create several indexes
Hello,
I created a multicolumn index on the columns c_1,..,c_n .
If I do use only a true subset of these columns in a SQL query, is the
index still efficient?
Or is it better to create another multicolumn index defined on this subset?
Thanks for any comments!
--
Sent via pgsql-performance mai
