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.1006011054270.4083@aragorn.flymine.org
Whole thread Raw
In response to Re: 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 Sun, 23 May 2010, David Jarvis wrote:
> The measurement table indexes (on date and weather station) were not being
> used because the only given date ranges (e.g., 1900 - 2009) were causing the
> planner to do a full table scan, which is correct.

I wonder if you might see some benefit from CLUSTERing the tables on the
index.

Matthew

--
 And the lexer will say "Oh look, there's a null string. Oooh, there's
 another. And another.", and will fall over spectacularly when it realises
 there are actually rather a lot.
         - Computer Science Lecturer (edited)

pgsql-performance by date:

Previous
From: Mindaugas Riauba
Date:
Subject: Re: Zeus IOPS
Next
From: Matthew Wakeling
Date:
Subject: Re: PostgreSQL Function Language Performance: C vs PL/PGSQL