Re: force index problem in 8.4.1

From: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: force index problem in 8.4.1
Date: 2009-11-26 06:55:56
Message-ID: Pine.LNX.4.64.0911260953060.6801@sn.sai.msu.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 25 Nov 2009, Tom Lane wrote:

> Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
>> I tried to force query to use index by specifying high execution cost, but
>> without success, even seqscan cost doesn't changed. This is 8.4.1
>
> I think you altered the wrong function. The function underlying
> point <@ box is on_pb() not pt_contained_box ... in fact, I don't
> even see a function named that.

sorry, I forgot to say, that I created operator

CREATE OR REPLACE FUNCTION pt_contained_box(point, box)
RETURNS bool
AS 'MODULE_PATHNAME'
LANGUAGE 'C'
IMMUTABLE RETURNS NULL ON NULL INPUT;

CREATE OPERATOR <@ (
LEFTARG = point,
RIGHTARG = box,
PROCEDURE = pt_contained_box,
COMMUTATOR = '@>',
RESTRICT = contsel,
JOIN = contjoinsel
);

Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg(at)sai(dot)msu(dot)su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2009-11-26 07:13:43 Re: operator exclusion constraints
Previous Message Heikki Linnakangas 2009-11-26 06:30:14 Re: Hot Standby and cancelling idle queries