<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Vector Database on Datalaria</title>
    <link>https://datalaria.com/en/tags/vector-database/</link>
    <description>Recent content in Vector Database on Datalaria</description>
    <generator>Hugo -- 0.148.2</generator>
    <language>en-US</language>
    <lastBuildDate>Tue, 22 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://datalaria.com/en/tags/vector-database/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PostgreSQL with pgvector vs Vector DBs: Why Almost Nobody Needs Pinecone</title>
      <link>https://datalaria.com/en/posts/pgvector_vs_vectordb/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://datalaria.com/en/posts/pgvector_vs_vectordb/</guid>
      <description>Do you really need a dedicated vector database like Pinecone, Qdrant, or Milvus? We analyze pgvector performance in PostgreSQL, the hidden operational cost of dual-database architectures, HNSW vs IVFFlat indexes, and why the unified database wins in 95% of real-world cases.</description>
    </item>
  </channel>
</rss>
