On Thu, 26 Nov 2009, Tom Lane wrote:
Oleg Bartunov writes:
On Wed, 25 Nov 2009, Tom Lane wrote:
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
Oleg Bartunov writes:
> On Wed, 25 Nov 2009, Tom Lane wrote:
>> 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
Unless you ch
On Wed, 25 Nov 2009, Tom Lane wrote:
Oleg Bartunov 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
Oleg Bartunov 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
Hi there,
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
=# explain select count(*) from spots where coordinates <@
'(0,0),(0.1,0.1)'::box;
QUERY PLAN
