Re: LIMIT causes planner to do Index Scan using a less optimal index

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: Sherry(dot)CTR(dot)Zhu(at)faa(dot)gov
Cc: Joel Jacobson <joel(at)gluefinance(dot)com>, pgsql-performance(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: LIMIT causes planner to do Index Scan using a less optimal index
Date: 2010-04-07 13:12:35
Message-ID: q2s2f4958ff1004070612ha4e21200uf29a00f9b1747968@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

2010/4/7 <Sherry(dot)CTR(dot)Zhu(at)faa(dot)gov>

>
> Do you mean one index on two columns?
>
> something like this: create index idx1 on tb1(col1, col2);
>
yup :) It would be quite useless without that feature.
Don't listen to oracle folks, they obviously know not much about products
others than oracle db(s).

--
GJ

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Sherry.CTR.Zhu 2010-04-07 13:22:51 Re: LIMIT causes planner to do Index Scan using a less optimal index
Previous Message Sherry.CTR.Zhu 2010-04-07 13:08:36 Re: LIMIT causes planner to do Index Scan using a less optimal index