X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 9FD699DC984 for ; Sun, 19 Mar 2006 02:26:47 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 57191-07 for ; Sun, 19 Mar 2006 02:26:47 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from ra.sai.msu.su (ra.sai.msu.su [158.250.29.2]) by postgresql.org (Postfix) with ESMTP id 7BE559DCD91 for ; Sun, 19 Mar 2006 02:26:38 -0400 (AST) Received: from ra (ra [158.250.29.2]) by ra.sai.msu.su (8.13.4/8.13.4) with ESMTP id k2J6QOpm007030; Sun, 19 Mar 2006 09:26:24 +0300 (MSK) Date: Sun, 19 Mar 2006 09:26:24 +0300 (MSK) From: Oleg Bartunov X-X-Sender: megera@ra.sai.msu.su To: Evgeny Gridasov cc: Dan Harris , pgsql-performance@postgresql.org Subject: Re: Help optimizing a slow index scan In-Reply-To: <20060317223253.38c0e6b9.eugene@i-free.ru> Message-ID: 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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.449 required=5 tests=[AWL=-0.030, DNS_FROM_RFC_ABUSE=0.479] X-Spam-Score: 0.449 X-Spam-Level: X-Archive-Number: 200603/313 X-Sequence-Number: 17750 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 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