Re: Forcing filter/join order?

Поиск
Список
Период
Сортировка
От Stephan Szabo
Тема Re: Forcing filter/join order?
Дата
Msg-id 20040218165410.G36125@megazone.bigpanda.com
обсуждение исходный текст
Ответ на Re: Forcing filter/join order?  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: Forcing filter/join order?  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-performance
On Wed, 18 Feb 2004, Josh Berkus wrote:

> The planner can't, or doesn't want to, use an index on (event_date,
> (event_date + duration)) where the first column is an ascending sort and the
> second a descending sort.    So I've coded a workaround that's quite
> inelegant but does get the correct results in 0.3 seconds (as opposed to the
> 2.2 seconds taken by the example plan).

Can you give more information?  I know that I'm not exactly certain what
the situation is from the above and the original query/explain piece.

В списке pgsql-performance по дате отправления:

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: Forcing filter/join order?
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: Forcing filter/join order?