From: Oleg Bartunov <oleg@sai.msu.su>
To: Evgeny Gridasov <eugene@i-free.ru>
Cc: Dan Harris <fbsd@drivefaster.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Help optimizing a slow index scan
Date: Sun, 19 Mar 2006 09:26:24 +0300 (MSK)
Message-ID: <Pine.GSO.4.63.0603190925180.6686@ra.sai.msu.su> (raw)
In-Reply-To: <20060317223253.38c0e6b9.eugene@i-free.ru>
References: <4419DB50.10404@drivefaster.net>
<4419DC1C.9070806@drivefaster.net>
<684362e10603161915x431c6b08t@mail.gmail.com>
<441AD702.9020508@drivefaster.net>
<441ADB88.9010701@drivefaster.net>
<20060317223253.38c0e6b9.eugene@i-free.ru>
On Fri, 17 Mar 2006, Evgeny Gridasov wrote:
> Try contrib/btree_gist.
contrib/btree_gist does nothing more than built-in btree - it's just
an support for multicolumn GiST indices.
> I've tried that one, but for my case it didn't help much.
> The performance was almost equal or even slower than built-in btree.
>
> On Fri, 17 Mar 2006 08:53:44 -0700
> Dan Harris <fbsd@drivefaster.net> wrote:
>
>> 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
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 5: don't forget to increase your free space map settings
>>
>
>
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: oleg@sai.msu.su, eugene@i-free.ru, fbsd@drivefaster.net
Subject: Re: Help optimizing a slow index scan
In-Reply-To: <Pine.GSO.4.63.0603190925180.6686@ra.sai.msu.su>
References: <4419DB50.10404@drivefaster.net> <4419DC1C.9070806@drivefaster.net> <684362e10603161915x431c6b08t@mail.gmail.com> <441AD702.9020508@drivefaster.net> <441ADB88.9010701@drivefaster.net> <20060317223253.38c0e6b9.eugene@i-free.ru> <Pine.GSO.4.63.0603190925180.6686@ra.sai.msu.su>
* 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