Re: Optimize date query for large child tables: GiST or GIN? - Mailing list pgsql-performance

From Matthew Wakeling
Subject Re: Optimize date query for large child tables: GiST or GIN?
Date
Msg-id alpine.DEB.2.00.1005201355020.23334@aragorn.flymine.org
Whole thread Raw
In response to Optimize date query for large child tables: GiST or GIN?  (David Jarvis <thangalin@gmail.com>)
Responses Re: Optimize date query for large child tables: GiST or GIN?
List pgsql-performance
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 by date:

Previous
From: Thom Brown
Date:
Subject: Re: Optimize date query for large child tables: GiST or GIN?
Next
From: Tom Lane
Date:
Subject: Re: Optimize date query for large child tables: GiST or GIN?