Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 7AEFA9FB39B for ; Wed, 1 Nov 2006 01:59:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 43652-02 for ; Wed, 1 Nov 2006 05:58:37 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 982119FB34D for ; Wed, 1 Nov 2006 01:58:27 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kA15wOGo013716; Wed, 1 Nov 2006 00:58:24 -0500 (EST) To: "Luke Lonergan" cc: "John Major" , pgsql-performance@postgresql.org Subject: Re: Help w/speeding up range queries? In-reply-to: References: Comments: In-reply-to "Luke Lonergan" message dated "Tue, 31 Oct 2006 21:26:04 -0800" Date: Wed, 01 Nov 2006 00:58:24 -0500 Message-ID: <13715.1162360704@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/4 X-Sequence-Number: 21774 "Luke Lonergan" 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