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

Do you mean one index on two columns?

something like this: create index idx1 on tb1(col1, col2);

Thanks much!

Xuefeng Zhu (Sherry)
Crown Consulting Inc. -- Oracle DBA
AIM Lab Data Team
(703) 925-3192

Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
04/07/2010 08:51 AM

To
Sherry CTR Zhu/AWA/CNTR/FAA(at)FAA
cc
Joel Jacobson <joel(at)gluefinance(dot)com>, pgsql-performance(at)postgresql(dot)org,
Robert Haas <robertmhaas(at)gmail(dot)com>
Subject
Re: [PERFORM] LIMIT causes planner to do Index Scan using a less optimal
index

On Wed, Apr 7, 2010 at 1:20 PM, <Sherry(dot)CTR(dot)Zhu(at)faa(dot)gov> wrote:

Guys,

Thanks for trying and opening your mind.
If you want to know how Oracle addressed this issue, here it is: index
on two columns. I remember that they told me in the training postgres has
no this kind of index, can someone clarify?

lies. postgresql allows you indices on multiple columns. What it does not
have, is index on multiple tables.

--
GJ