News for hackers. Stuff that matters.
Re:Pgvector – vector similarity search for Postgres by gk1 on Thursday April 22, 2021 @01:19PM (#26905278)
Why are they a pain in the...?
Re:Pgvector – vector similarity search for Postgres by EmilStenstrom on Thursday April 22, 2021 @02:32PM (#26906252)
They typically load all data in memory, so you still need persistence to handle crashes (two setups). And since data is typically huge you need servers with lots of expensive RAM.
Re:Pgvector – vector similarity search for Postgres by patelajay285 on Thursday April 22, 2021 @03:09PM (#26906833)
Check out Magnitude, we built it to solve that problem: https://github.com/plasticityai/magnitude

It's still loaded from a file, but heavily uses memory-mapping and caching to be speedy and not overload your RAM immediately. And in production scenarios, multiple worker processes can share that memory due to the memory mapping.

Granted it's read-only, so might not be exactly what you are looking for.

Disclaimer: I'm the author.

Re:Pgvector – vector similarity search for Postgres by rkt08 on Thursday April 22, 2021 @03:20PM (#26906974)
How about a vector oriented 'database' instead? Pinecone(https://www.pinecone.io/) does both exact and approx search and it's fully managed so you don't have to worry about reliability,availability etc.

PS: I work there

Re:Pgvector – vector similarity search for Postgres by phenkdo on Thursday April 22, 2021 @01:43PM (#26905574)
the usual yet-another-moving-part (YAMP) complexity.