From: | Dan Harris <fbsd(at)drivefaster(dot)net> |
---|---|
To: | PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Help optimizing a slow index scan |
Date: | 2006-03-17 15:53:44 |
Message-ID: | 441ADB88.9010701@drivefaster.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2006-03-17 15:59:16 | Re: 1 TB of memory |
Previous Message | Dan Harris | 2006-03-17 15:34:26 | Re: Help optimizing a slow index scan |