Re: Question on "box @> point" using GiST index on boxes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ralf Rantzau <rrantzau(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Question on "box @> point" using GiST index on boxes
Date: 2012-10-04 03:07:51
Message-ID: 13902.1349320071@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ralf Rantzau <rrantzau(at)gmail(dot)com> writes:
> I would like to test the containment of a point against many boxes.
> I did not find a way to express "box @> point" in straightforward way such
> that the GiST index on the boxes is exploited.

Yeah, that operator is not in any GiST opclass, as you can easily verify
with a look into pg_amop. It seems like it probably wouldn't be
terribly hard to add it (and related box vs point operators) to GiST
box_ops, but nobody's bothered to do the legwork.

> The way I currently represent a point p is as: box(p, p). In this case,
> the GiST index use kicks in.

Right, that's the standard workaround. Note that I'm not sure that
direct use of the box vs point operators would be any faster, but it'd
surely be less surprising.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2012-10-04 03:24:31 Re: [PATCH] Make pg_basebackup configure and start standby [Review]
Previous Message Craig Ringer 2012-10-04 02:56:06 Docs bug: SET ROLE docs should "see also: DISCARD ALL"