Re: Cube extension kNN support

From: Stas Kelvich <stas(dot)kelvich(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Teodor Sigaev <teodor(at)sigaev(dot)ru>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Cube extension kNN support
Date: 2015-12-16 14:31:33
Message-ID: 75E00538-B701-4CAD-95F2-69A9FBD78B0F@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I don't think that's what the comment says, actually. It rather refers to code like this:
>
> result = Min(LL_COORD(c, n - 1), UR_COORD(c, n - 1));
>
> i.e. if you specifically ask for a particular corner (ll, in this case), you'll get the proper value.

Hmm, I was confused by phrase “create a uniform _internal_ representation” and actually internally cube stored “as is”. But probably i just misinterpret that.
So here is the updated version with old documentation restored.

Attachment Content-Type Size
cube_distances.patch application/octet-stream 66.3 KB
unknown_filename text/plain 2.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2015-12-16 16:02:29 Re: Performance improvement for joins where outer side is unique
Previous Message Alvaro Herrera 2015-12-16 14:03:07 Re: Re: Potential pointer dereference in plperl.c (caused by transforms patch)