Vector databases: analyzing the trade-offs

Re:Vector databases: analyzing the trade-offs by dmezzetti on Sunday August 20, 2023 @05:19PM (#37203010)

pg_vector doesn't perform well compared to other methods, at least according to ANN-Benchmarks (https://ann-benchmarks.com/).

txtai is more than just a vector database. It also has a built-in graph component for topic modeling that utilizes the vector index to autogenerate relationships. It can store metadata in SQLite/DuckDB with support for other databases coming. It has support for running LLM prompts right with the data, similar to a stored procedure, through workflows. And it has built-in support for vectorizing data into vectors.

For vector databases that simply store vectors, I agree that it's nothing more than just a different index type.

[ Parent | on HN ]

Re:Vector databases: analyzing the trade-offs by askIoT on Sunday August 20, 2023 @10:10PM (#37204764)

I find the utility of pg_vector very useful since it also acts as the default DB for a ton of other functions. Interested to see if folks think that a combination of postgres with something like qdrant is the way to go? is the benefits worth the trade off in terms of ease of use and flexibility.

[ Parent | on HN ]