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

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 12:51:17
Message-ID: o2l2f4958ff1004070551o30fe9871g17fe164a5fdd36af@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
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

In response to

Responses

pgsql-performance by date

Next:From: Sherry.CTR.ZhuDate: 2010-04-07 13:08:36
Subject: Re: LIMIT causes planner to do Index Scan using a less optimal index
Previous:From: Sabin CoandaDate: 2010-04-07 12:47:54
Subject: How check execution plan of a function

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