From: | A B <gentosaker(at)gmail(dot)com> |
---|---|
To: | postgresql Forums <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Index on points |
Date: | 2010-09-27 05:17:53 |
Message-ID: | AANLkTimCVn=kyP14z9YQ35TWw+hVn4i67VneNAQ90S8O@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sorry, Gmail made med confused, my biggest "thank you" was to Richard
Huxton, who showed me code that worked.
2010/9/26 A B <gentosaker(at)gmail(dot)com>:
> 2010/9/25 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> Jeff Davis <pgsql(at)j-davis(dot)com> writes:
>>> There's no reason that there couldn't be a point <@ box operator in the
>>> opclass, but nobody really uses these geometric types that come with
>>> core postgres (at least, not that I can tell).
>>
>> Actually, as of 9.0 there is a point_ops opclass for GIST, with these
>> indexable operators:
>>
>> >^(point,point)
>> <<(point,point)
>> >>(point,point)
>> <^(point,point)
>> ~=(point,point)
>> <@(point,box)
>> <@(point,polygon)
>> <@(point,circle)
>>
>> I agree that for any more than light-duty geometric work, you ought
>> to look at PostGIS.
>>
>> regards, tom lane
>
> Thank you Jeff for your reply, that solved the problem.
>
> Tom, would you like to elaborate on that PostGIS should be used for
> other than "light-duty" geometric work?
> Is it speed, accuracy or features that is the difference?
> For this project I think <@(point,box) is sufficient. What would it
> take to motivate a switch to PostGIS for that?
>
> Best wishes.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Padmanabha, Shruthi (UMKC-Student) | 2010-09-27 05:30:31 | Database Cluster Initialisation Failed" error during PostgreSQL install |
Previous Message | Guillaume Lelarge | 2010-09-27 05:06:43 | Re: Checking for stale reads on hot standby |