Re: Planner create a slow plan without an available index

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Ben-Nes Yonatan <da(at)canaan(dot)co(dot)il>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Planner create a slow plan without an available index
Date: 2005-08-30 12:47:25
Message-ID: 20050830124725.GC22545@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Aug 30, 2005 at 11:25:26 +0200,
Ben-Nes Yonatan <da(at)canaan(dot)co(dot)il> wrote:
>
> If btree index is not suitable for this query then which index is? as
> far as I understand the rtree index doesnt support range checks and the
> hash index is not recommended by almost everyone (including the manual)
> so the only one left is the gist, is that the most suitable index for
> this query? if so can you give me a link as to where I can learn how to
> use such an index efficently? (by the way the only link that worked at
> the postgresql manual "Chapter 48. GiST Indexes" is the one which direct
> to "the University of California at Berkeley's GiST Indexing Project web
> site" the other 2 links direct to 404 pages and I guess that they should
> be removed).

rtree indexes allow you to quickly check for containment. Range checking
is one dimensional containment.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Reid Thompson 2005-08-30 12:49:40 Re: Select gives the wrong results
Previous Message Michael Fuhr 2005-08-30 12:06:56 Re: temp_buffers