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

From Alvaro Herrera
Subject Re: Optimize date query for large child tables: GiST or GIN?
Date
Msg-id 1275412319-sup-2359@alvh.no-ip.org
Whole thread Raw
In response to Re: Optimize date query for large child tables: GiST or GIN?  (Matthew Wakeling <matthew@flymine.org>)
Responses Re: Optimize date query for large child tables: GiST or GIN?
List pgsql-performance
Excerpts from Matthew Wakeling's message of mar jun 01 05:55:35 -0400 2010:
> 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.

Eh, isn't this a GIN or GiST index?  I don't think you can cluster on
those, can you?

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-performance by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: PostgreSQL Function Language Performance: C vs PL/PGSQL
Next
From: Alvaro Herrera
Date:
Subject: Re: Optimize date query for large child tables: GiST or GIN?