| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru> |
| Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, <emre(at)hasegeli(dot)com>, 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-22 15:40:22 |
| Message-ID: | 56F16766.1090305@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/21/16 7:41 PM, Stas Kelvich wrote:
> While people tends to use machine learning and regressions models more and more it is interesting to have some general n-dim indexing with kNN,
> but I think it is different problem and should be solved in a different way.
I think one of the issues here is it's not very clear to someone without
a good amount of ML knowledge how these things relate. I hear "box' and
'cube' and think it's just a 2D vs 3D issue, and intarray isn't even on
the radar.
Maybe what's needed are actual vector and matrix types?
In any case, if you've got a good reason why box and cube should stay
separate then further discussion should happen in another thread.
BTW, if you haven't seen it, take a look at http://madlib.apache.org/
--
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 | Magnus Hagander | 2016-03-22 15:41:37 | Re: Password identifiers, protocol aging and SCRAM protocol |
| Previous Message | Alvaro Herrera | 2016-03-22 15:24:26 | Re: Some messages of pg_rewind --debug not getting translated |