Re: GiST limits on contrib/cube with dimension > 100? - Mailing list pgsql-hackers

From Siarhei Siniak
Subject Re: GiST limits on contrib/cube with dimension > 100?
Date
Msg-id 107554388.279124.1560334265812@mail.yahoo.com
Whole thread Raw
In response to Re: GiST limits on contrib/cube with dimension > 100?  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: GiST limits on contrib/cube with dimension > 100?  (Andrey Borodin <x4mmm@yandex-team.ru>)
List 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.

pgsql-hackers by date:

Previous
From:
Date:
Subject: RE: BEFORE UPDATE trigger on postgres_fdw table not work
Next
From: Peter Eisentraut
Date:
Subject: Re: check_recovery_target_lsn() does a PG_CATCH without a throw