Re: GiST limits on contrib/cube with dimension > 100?

From: Siarhei Siniak <siarheisiniak(at)yahoo(dot)com>
To: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GiST limits on contrib/cube with dimension > 100?
Date: 2019-06-12 10:11:05
Message-ID: 107554388.279124.1560334265812@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

A uniform set of points with a dimension 128 and type cube. That has a size of 50 ** 3. Can be queried for a nearest neighbor at a speed of 10 queries per second with limit varying from 1 to 25.
It works better than when no index used at all. So gist gives here a speed up.
The documentation of postgresql doesn't mention complexity of such an index. I've got confused as to its speed.
Does postgresql allow for an approximate nearest neighbor search?
https://github.com/erikbern/ann-benchmarks has a lot of efficient implementations.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-06-12 11:16:54 Re: check_recovery_target_lsn() does a PG_CATCH without a throw
Previous Message shohei.mochizuki 2019-06-12 09:08:50 RE: BEFORE UPDATE trigger on postgres_fdw table not work