Postgres vs. Pinecone
lantern.dev
Postgres vs. Pinecone
1–10 of 20 posts
Re: Postgres vs. Pinecone
#2Wow this should be getting a lot more love. I wonder if you could do a breakdown vs Qdrant?
Re: Postgres vs. Pinecone
#3Indexing in Postgres is legitimately painful, I don’t think “get moar ram” is a good response to that particular critique.
Re: Postgres vs. Pinecone
#4PostgreSQL is Enough
https://gist.github.com/cpursley/c8fb81fe8a7e5df038158bdfe0f...
Re: Postgres vs. Pinecone
#5Vector dbs are quickly becoming a commodity. This was not true when pinecone was founded and received its first few rounds of funding.
At this point, Postgres has clearly caught up and the VCs are going to do everything it takes to hold on.
Re: Postgres vs. Pinecone
#6Vector dbs are quickly becoming a commodity. This was not true when pinecone was founded and received its first few rounds of funding. At this point, Postgres has clearly caught up and the VCs are going to do everything it takes to hold on.
Vectors seem like kinda the easiest thing to store in a lot of ways
Re: Postgres vs. Pinecone
#7Vector dbs are quickly becoming a commodity. This was not true when pinecone was founded and received its first few rounds of funding. At this point, Postgres has clearly caught up and the VCs are going to do everything it takes to hold on.
Pinecone just put devops around facebooks FAISS library
Re: Postgres vs. Pinecone
#8[deleted]
Re: Postgres vs. Pinecone
#9The venn diagram of "problems that people have" and "problems that postgres solves" is closer to a circle than many would like to admit.
Re: Postgres vs. Pinecone
#10Indexing in Postgres is legitimately painful, I don’t think “get moar ram” is a good response to that particular critique.
Neither is it a good demonstration of things that people who currently maintain postgres are experienced in doing. Companies should be reluctant to manage their own vector indexes until this becomes more a more mainstream skillset.
This excellent blog post[1] demonstrates the complexities of scaling HNSW indexes and shows that at a certain point, you need to switch to ivfpq with vastly different performance and accuracy characteristics.
https://aws.amazon.com/blogs/big-data/choose-the-k-nn-algori...