pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Dan Harris <fbsd@drivefaster.net>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Help optimizing a slow index scan
Date: Fri, 17 Mar 2006 11:38:27 -0600
Message-ID: <20060317173827.GB15967@wolff.to> (raw)
In-Reply-To: <441AD702.9020508@drivefaster.net>
References: <4419DB50.10404@drivefaster.net>
	<4419DC1C.9070806@drivefaster.net>
	<684362e10603161915x431c6b08t@mail.gmail.com>
	<441AD702.9020508@drivefaster.net>

On Fri, Mar 17, 2006 at 08:34:26 -0700,
  Dan Harris <fbsd@drivefaster.net> wrote:
> Markus Bertheau wrote:
> >Have you tried using a GIST index on lat & long? These things are
> >meant for two-dimensional data, whereas btree doesn't handle
> >two-dimensional data that well. How many rows satisfy either of the
> >long / lat condition?
> >
> >  
> >>    
> According to the analyze, less than 500 rows matched.  I'll look into 
> GIST indexes, thanks for the feedback.

Have you looked at using the Earth Distance contrib module? If a spherical
model of the earth is suitable for your application, then it may work for you
and might be easier than trying to create Gist indexes yourself.



view thread (15+ messages)  latest in thread

Message-ID: <20060317173827.GB15967@wolff.to>
Permalink:  ../20060317173827.GB15967@wolff.to/
Also on:    postgresql.org/message-id/20060317173827.GB15967@wolff.to

 · 

reply

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: bruno@wolff.to, fbsd@drivefaster.net
  Subject: Re: Help optimizing a slow index scan
  In-Reply-To: <20060317173827.GB15967@wolff.to>

* 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