| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, <emre(at)hasegeli(dot)com> |
| Cc: | Oleg Bartunov <obartunov(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Alexander Lebedev <a(dot)lebedev(at)postgrespro(dot)ru> |
| Subject: | Re: [PATCH] we have added support for box type in SP-GiST index |
| Date: | 2016-03-21 22:47:16 |
| Message-ID: | 56F079F4.3070804@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/21/16 11:57 AM, Teodor Sigaev wrote:
> A and B are points of intersection of lines. So, box PBCAis a bounding
> box for points contained in 3-rd (see labeling above). For example X
> labeled point is not a descendace of child node with centroid C because
> it must be in branch of 1-st quad of parent node. So, each node (except
> root) will have a limitation in its quadrant. To transfer that
> limitation the traversalValue is used.
Isn't this basically the same thing that the cube contrib module does?
(Which has the added benefit of kNN-capable operators).
If that's true then ISTM it'd be better to work on pulling cube's
features into box?
If it's not true, I'm still wondering if there's enough commonality here
that we should pull cube into core...
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-03-21 22:49:55 | Re: Relax requirement for INTO with SELECT in pl/pgsql |
| Previous Message | Stephen Frost | 2016-03-21 22:38:01 | Re: Minor bug affecting ON CONFLICT lock wait log messages |