Postgres Pro
Downloads
Home   >   mailing lists

Re: LIMIT causes planner to do Index Scan using a less optimal index - Mailing list pgsql-performance

From Grzegorz Jaśkiewicz
Subject Re: LIMIT causes planner to do Index Scan using a less optimal index
Date
Msg-id o2l2f4958ff1004070551o30fe9871g17fe164a5fdd36af@mail.gmail.com
Whole thread Raw
In response to Re: LIMIT causes planner to do Index Scan using a less optimal index  (Sherry.CTR.Zhu@faa.gov)
Responses Re: LIMIT causes planner to do Index Scan using a less optimal index
List pgsql-performance
Tree view


On Wed, Apr 7, 2010 at 1:20 PM, <Sherry.CTR.Zhu@faa.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

pgsql-performance by date:

Previous
From: Sherry.CTR.Zhu@faa.gov
Date:
Subject: Re: LIMIT causes planner to do Index Scan using a less optimal index
Next
From: Sherry.CTR.Zhu@faa.gov
Date:
Subject: Re: LIMIT causes planner to do Index Scan using a less optimal index