Martijn van Oosterhout writes:
> If you want index support, you need to go the whole way, and setup an
> appropriate operator class for (box,point).
No, I think he's doing the right thing by adding these cross-type
operators "loose" in the opfamily. An operator class is the subset
of an opfamily
On Fri, Aug 21, 2009 at 09:42:57PM +1000, Paul Matthews wrote:
> Martijn van Oosterhout wrote:
> > I haven't completely understood what you're trying to do
> >
> Putting in place the missing 'box op point' and 'point op box'
> operators. The problematic queries are at the bottom of the email.
I
Paul Matthews writes:
> The C function? No it seems OK as well. What am I missing?
Did you teach the opclass's consistent() function about these new
operators?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to you
Martijn van Oosterhout wrote:
> I haven't completely understood what you're trying to do
>
Putting in place the missing 'box op point' and 'point op box'
operators. The problematic queries are at the bottom of the email.
> - I don't see any definition of an operator class, just the family,
> w
On Fri, Aug 21, 2009 at 08:28:05PM +1000, Paul Matthews wrote:
> Trying to solve this problem by using a process of elimination. All
> works fine until the comment below is removed.
I haven't completely understood what you're trying to do, but I have a
few points.
- I don't see any definition of
Trying to solve this problem by using a process of elimination. All
works fine until the comment below is removed.
ALTER OPERATOR FAMILY box_ops USING GiST ADD
OPERATOR 1 << (box,point),
OPERATOR 2 &< (box,point),
OPERATOR 3 && (box,point),
OPERATOR 4 &> (box,point),
OPERATOR 5
