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

Поиск
Список
Период
Сортировка
От Grzegorz Jaśkiewicz
Тема Re: LIMIT causes planner to do Index Scan using a less optimal index
Дата
Msg-id o2l2f4958ff1004070551o30fe9871g17fe164a5fdd36af@mail.gmail.com
обсуждение исходный текст
Ответ на Re: LIMIT causes planner to do Index Scan using a less optimal index  (Sherry.CTR.Zhu@faa.gov)
Ответы Re: LIMIT causes planner to do Index Scan using a less optimal index  (Sherry.CTR.Zhu@faa.gov)
Список pgsql-performance
Дерево обсуждения


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 по дате отправления:

Предыдущее
От: Sherry.CTR.Zhu@faa.gov
Дата:
Сообщение: Re: LIMIT causes planner to do Index Scan using a less optimal index
Следующее
От: Sherry.CTR.Zhu@faa.gov
Дата:
Сообщение: Re: LIMIT causes planner to do Index Scan using a less optimal index