Re: Help optimizing a slow index scan
- From: Bruno Wolff III <bruno(at)wolff(dot)to>
- To: Dan Harris <fbsd(at)drivefaster(dot)net>
- Cc: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
- Subject: Re: Help optimizing a slow index scan
- Date: Fri, 17 Mar 2006 11:38:27 -0600
- Message-id: <20060317173827(dot)GB15967(at)wolff(dot)to>
On Fri, Mar 17, 2006 at 08:34:26 -0700,
Dan Harris <fbsd(at)drivefaster(dot)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.
Home |
Main Index |
Thread Index