From: Tom Lane <tgl@sss.pgh.pa.us>
To: Luke Lonergan <llonergan@greenplum.com>
Cc: John Major <major@cbio.mskcc.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Help w/speeding up range queries?
Date: Wed, 01 Nov 2006 00:58:24 -0500
Message-ID: <13715.1162360704@sss.pgh.pa.us> (raw)
In-Reply-To: <C16D6FEC.5991%llonergan@greenplum.com>
References: <C16D6FEC.5991%llonergan@greenplum.com>
"Luke Lonergan" <llonergan@greenplum.com> writes:
> Oops - I missed the point earlier. Start and End are separate attributes so
> this is like an unbounded window in a Start,End space. PostGis provides
> quadtree indexing would provide a terse TID list but you still have the
> problem of how to ensure that the heap tuples being scanned are efficiently
> retrieved, which would only happen if they are grouped similarly to the
> retrieval pattern, right?
Yeah, but I think that's a second-order problem compared to having an
index that's reasonably well matched to the query ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, llonergan@greenplum.com, major@cbio.mskcc.org
Subject: Re: Help w/speeding up range queries?
In-Reply-To: <13715.1162360704@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox