Re:Choosing vector database: a side-by-side comparison
by mritchie712 on Wednesday October 04, 2023 @12:08PM
(#37767224)
Same for Developer experience. If you used Postgres or any other relational db (which I think covers a large % of devs), you could easily argue the dev experience is 3/3 for pgvector.
[ Parent
| on HN ]
Re:Choosing vector database: a side-by-side comparison
by jaggederest on Wednesday October 04, 2023 @07:07PM
(#37772972)
Not only 3/3 but also includes full text search built in. Tables look like:
MyThingEmbedding
______
id primary key
mything_id integer -- fkey to mything table
embedding vector(1536)
fulltext tsvector
GIN index on tsvector
HSNW index on embedding
Then you can pull results that match either the tsvector AND/OR the similarity with a single query, and it's pretty performant. You can also choose at the query level whether you want exact matching or fuzzy.