From: Dan Harris <fbsd@drivefaster.net>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Help optimizing a slow index scan
Date: Fri, 17 Mar 2006 08:53:44 -0700
Message-ID: <441ADB88.9010701@drivefaster.net> (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>
Dan Harris 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.
>
> -Dan
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
When I try to create a GIST index, I get the following error:
create index eventgeo_lat_idx on eventgeo using GIST (lat);
ERROR: data type double precision has no default operator class for
access method "gist"
HINT: You must specify an operator class for the index or define a
default operator class for the data type.
I'm not sure what a "default operator class" is, exactly..
-Dan
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: fbsd@drivefaster.net
Subject: Re: Help optimizing a slow index scan
In-Reply-To: <441ADB88.9010701@drivefaster.net>
* 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