Re:Using Your Vector Database as a JSON (Or Relational) Data...
by w1 on Tuesday April 23, 2024 @12:21AM
(#40128473)
Postgres (with pgvector) is an unbelievably goated vector db. Idk why anyone would use anything else.
[ Parent
| on HN ]
Re:Using Your Vector Database as a JSON (Or Relational) Data...
by stephen37 on Tuesday April 23, 2024 @03:50AM
(#40129576)
It's nice to begin with but you usually quickly hit a scale issue from what I tried and talked to different people using it.
Also they only offer index stored in Memory as far as I know, also lack the support of different index or more advanced ones like GPU index.
Re:Using Your Vector Database as a JSON (Or Relational) Data...
by brigadier132 on Tuesday April 23, 2024 @01:57AM
(#40128946)
PgVector stores the index in memory right? Do you really want your primary db using all its memory for vectors and all its cpu for doing vector dot products?
Re:Using Your Vector Database as a JSON (Or Relational) Data...
by Bella-Xiang on Tuesday April 23, 2024 @01:48AM
(#40128902)
There are significant differences in performance, accuracy, and other aspects when using a general-purpose database like PostgreSQL. These differences can lead to bottlenecks in performance and data scale. You can refer to this comparison article to learn more
https://myscale.com/blog/myscale-vs-postgres-opensearch/
Re:Using Your Vector Database as a JSON (Or Relational) Data...
by trosterud on Tuesday April 23, 2024 @07:12AM
(#40130518)
And Datomic is the goat outside of vectors
Re:Using Your Vector Database as a JSON (Or Relational) Data...
by manishsharan on Tuesday April 23, 2024 @09:37AM
(#40131824)
So you want to run mission critical workloads on Postgres and do a vector similarity search on the same DB?