Re: CUBE_MAX_DIM - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CUBE_MAX_DIM
Date
Msg-id 2277294.1593103392@sss.pgh.pa.us
Whole thread Raw
In response to Re: CUBE_MAX_DIM  (Alastair McKinley <a.mckinley@analyticsengines.com>)
Responses Re: CUBE_MAX_DIM  (Alastair McKinley <a.mckinley@analyticsengines.com>)
List pgsql-hackers
Alastair McKinley <a.mckinley@analyticsengines.com> writes:
> I know that Cube in it's current form isn't suitable for nearest-neighbour searching these vectors in their raw form
(Ihave tried recompilation with higher CUBE_MAX_DIM myself), but conceptually kNN GiST searches using Cubes can be
usefulfor these applications.  There are other pre-processing techniques that can be used to improved the speed of the
search,but it still ends up with a kNN search in a high-ish dimensional space. 

Is there a way to fix the numerical instability involved?  If we could do
that, then we'd definitely have a use-case justifying the work to make
cube toastable.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Default setting for enable_hashagg_disk
Next
From: Alvaro Herrera
Date:
Subject: Re: Weird failures on lorikeet