| From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Stefan Keller <sfkeller(at)gmail(dot)com> |
| Cc: | Emre Hasegeli <emre(at)hasegeli(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: point_ops for GiST |
| Date: | 2015-10-12 09:24:40 |
| Message-ID: | CAPpHfduvEE_UeqcDqVgFXt=4bv788aut-qE6sms1bJDL2Nkt1A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi, Stefan!
On Sun, Oct 11, 2015 at 10:00 PM, Stefan Keller <sfkeller(at)gmail(dot)com> wrote:
> Pls. don't misunderstand my questions: They are directed to get an
> even more useful spatial data handling of PostgreSQL. I'm working with
> PostGIS since years and are interested in any work regarding spatial
> types...
>
> Can anyone report use cases or applications of these built-in geometric
> types?
>
> Would'nt it be even more useful to concentrate to PostGIS
> geometry/geography types and extend BRIN to these types?
>
Note, that PostGIS is a different project which is maintained by separate
team. PostGIS have its own priorities, development plan etc.
PostgreSQL have to be self-consistent. In particular, it should have
reference implementation of operator classes which extensions can use as
the pattern. This is why it's important to maintain built-in geometric
types.
In short: once we implement it for built-in geometric types, you can ask
PostGIS team to do the same for their geometry/geography.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emre Hasegeli | 2015-10-12 09:47:21 | Re: point_ops for GiST |
| Previous Message | Alexander Korotkov | 2015-10-12 09:17:10 | Re: point_ops for GiST |