Re: Optimize date query for large child tables: GiST or GIN?

Поиск
Список
Период
Сортировка
Искать
От
Matthew Wakeling
Тема
Re: Optimize date query for large child tables: GiST or GIN?
Дата
в 10:03:21
Msg-id
alpine.DEB.2.00.1005201355020.23334@aragorn.flymine.org
Ответ на
Optimize date query for large child tables: GiST or GIN? (David Jarvis)
Список
Дерево обсуждения
Optimize date query for large child tables: GiST or GIN? David Jarvis <thangalin@gmail.com>
Re: Optimize date query for large child tables: GiST or GIN? Stephen Frost <sfrost@snowman.net>
Re: Optimize date query for large child tables: GiST or GIN? David Jarvis <thangalin@gmail.com>
Re: Optimize date query for large child tables: GiST or GIN? Yeb Havinga <yebhavinga@gmail.com>
Re: Optimize date query for large child tables: GiST or GIN? Thom Brown <thombrown@gmail.com>
Re: Optimize date query for large child tables: GiST or GIN? Matthew Wakeling <matthew@flymine.org>
Re: Optimize date query for large child tables: GiST or GIN? Tom Lane <tgl@sss.pgh.pa.us>
Re: Optimize date query for large child tables: GiST or GIN? David Jarvis <thangalin@gmail.com> 
On Wed, 19 May 2010, David Jarvis wrote:
>      extract( YEAR FROM m.taken ) BETWEEN 1900 AND 2009 AND

That portion of the WHERE clause cannot use an index on m.taken. Postgres 
does not look inside functions (like extract) to see if something 
indexable is present. To get an index to work, you could create an index 
on (extract(YEAR FROM m.taken)).

Matthew

-- 
 Here we go - the Fairy Godmother redundancy proof.
                                        -- Computer Science Lecturer
В списке pgsql-performance по дате отправления
Предыдущее
От: Thom Brown
Дата:
Следующее
От: Tom Lane
Дата:
FAQ