<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>xieydd on Vchord</title>
    <link>https://vchord.pgsty.com/authors/xieydd/</link>
    <description>Recent content in xieydd on Vchord</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    
    
    
      <lastBuildDate>Tue, 03 Nov 2026 01:15:06 +0800</lastBuildDate>
    
    
      <atom:link href="https://vchord.pgsty.com/authors/xieydd/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>VectorChord 0.5: New RaBitQ-empowered DiskANN Index and Continuous Recall Measurement</title>
        <link>https://vchord.pgsty.com/blog/release/vectorchord-05-new-rabitq-empowered-diskann-index-and-continuous-recall-measurement/</link>
        <pubDate>Fri, 26 Sep 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/release/vectorchord-05-new-rabitq-empowered-diskann-index-and-continuous-recall-measurement/</guid>
        <description>&lt;p&gt;We&amp;rsquo;re thrilled to announce the release of &lt;strong&gt;VectorChord 0.5&lt;/strong&gt;! This release marks a significant step forward in our mission to provide more flexible, powerful, and controllable vector search capabilities. In the 0.5 release, we&amp;rsquo;re introducing two major updates: &lt;strong&gt;experimental support for the DiskANN graph index&lt;/strong&gt; and a new &lt;strong&gt;recall measurement tool to monitor the health of your IVF+RaBitQ indexes proactively&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;new-index-preview-rabitq-empowered-diskann-index&#34;&gt;New Index Preview: RaBitQ-empowered DiskANN Index&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;From day one, VectorChord&amp;rsquo;s core indexing solution has relied on a powerful combination: the cluster-based IVF algorithm and RaBitQ quantization—what we ship as &lt;strong&gt;vchordrq (IVF+RaBitQ)&lt;/strong&gt;. This approach consistently delivers excellent low-latency, high-recall performance across a wide range of use cases and remains &lt;strong&gt;our recommended default&lt;/strong&gt; for most scenarios.&lt;/p&gt;</description>
      </item>
    <item>
        <title>All-in-one VectorChord Suite: Building Production-Ready RAG Solutions Directly in PostgreSQL</title>
        <link>https://vchord.pgsty.com/blog/post/all-in-one-vectorchord-suite-building-production-ready-rag-solutions-directly-in-postgresql/</link>
        <pubDate>Tue, 29 Apr 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/all-in-one-vectorchord-suite-building-production-ready-rag-solutions-directly-in-postgresql/</guid>
        <description>&lt;p&gt;Retrieval-Augmented Generation (RAG) is revolutionizing our interaction with vast datasets and language models. RAG systems offer more precise, contextually aware, and current answers by retrieving pertinent information before generating responses. Nonetheless, constructing robust, scalable, and efficient RAG pipelines poses considerable challenges, particularly for production use.&lt;/p&gt;&#xA;&lt;p&gt;Many solutions feature complex architectures, using distinct databases for vector search, keyword search, and primary data storage. This commonly results in data synchronization challenges, greater infrastructure complexity, and higher operational costs.&lt;/p&gt;</description>
      </item>
    <item>
        <title>Beyond Text: Unlock OCR-Free RAG in PostgreSQL with Modal &amp; VectorChord</title>
        <link>https://vchord.pgsty.com/blog/post/beyond-text-unlock-ocr-free-rag-in-postgresql-with-modal-and-vectorchord/</link>
        <pubDate>Tue, 15 Apr 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/beyond-text-unlock-ocr-free-rag-in-postgresql-with-modal-and-vectorchord/</guid>
        <description>&lt;p&gt;Building effective Retrieval-Augmented Generation (RAG) systems for documents often feels like wrestling with messy, complex pipelines. Especially when dealing with PDFs or scanned images, traditional methods rely heavily on Optical Character Recognition (OCR) and layout analysis. These steps can be slow, error-prone, and often lose crucial visual context like tables, figures, and formatting. &lt;strong&gt;But what if you could query documents based on &lt;em&gt;how they look&lt;/em&gt;, not just the extracted text?&lt;/strong&gt;&lt;/p&gt;</description>
      </item>
    <item>
        <title>Vector Search Over PostgreSQL: A Comparative Analysis of Memory and Disk Solutions</title>
        <link>https://vchord.pgsty.com/blog/post/vector-search-over-postgresql-a-comparative-analysis-of-memory-and-disk-solutions/</link>
        <pubDate>Thu, 03 Apr 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/vector-search-over-postgresql-a-comparative-analysis-of-memory-and-disk-solutions/</guid>
        <description>&lt;h2 id=&#34;introduction-real-world-challenges&#34;&gt;Introduction: real-world challenges&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Specialized vector databases aren’t always needed. With PostgreSQL extensions like &lt;a href=&#34;https://vchord.pgsty.com/docs/vector/&#34;&gt;pgvector&lt;/a&gt;, &lt;a href=&#34;https://github.com/timescale/pgvectorscale&#34;&gt;pgvectorscale&lt;/a&gt;, &lt;a href=&#34;https://vchord.pgsty.com/docs/vchord/&#34;&gt;VectorChord&lt;/a&gt; (which evolved from &lt;a href=&#34;https://vchord.pgsty.com/docs/vectors/&#34;&gt;pgvecto.rs&lt;/a&gt;)****, you get vector search &lt;em&gt;plus&lt;/em&gt; relational power—no extra infrastructure. But adoption isn’t seamless. Here’s what real users say:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;The query &lt;strong&gt;takes 30 seconds&lt;/strong&gt; for the first time and 100ms if it&amp;rsquo;s a repeat query. The problem is very slow IO.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Is it normal to take 3 hours to build the index for 12 million rows with 75 dimension vector?&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;After 13 hours of building index for 200 million vectors of 75 dimensions each, I have noticed a heavy memory usage at 100GB/124GB at 30% of building index, and server will eventually crash.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;We&amp;rsquo;re hitting some challenges, particularly around need for frequent index updates, throughput constraints, lack of parallel index scans and no built-in quantization.&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/blockquote&gt;</description>
      </item>
    <item>
        <title>Hybrid search with Postgres Native BM25 and VectorChord</title>
        <link>https://vchord.pgsty.com/blog/post/hybrid-search-with-postgres-native-bm25-and-vectorchord/</link>
        <pubDate>Thu, 13 Mar 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/hybrid-search-with-postgres-native-bm25-and-vectorchord/</guid>
        <description>&lt;p&gt;In the era of RAG (Retrieval-Augmented Generation), efficiently retrieving relevant data from vast datasets is crucial for businesses and developers. Traditional keyword-based retrieval methods, such as those utilizing &lt;strong&gt;BM25&lt;/strong&gt; as a scoring mechanism, excel in ranking documents based on term frequency and exact keyword matches. This makes them highly effective for structured queries and keyword-heavy content. However, they struggle with understanding synonyms, contextual nuances, and semantic intent. Conversely, vector-based retrieval captures deep semantic meaning, enabling better generalization across varied queries but sometimes sacrificing precision in exact keyword matches. Hybrid Search bridges this gap by combining BM25’s precision with vector search’s contextual understanding, delivering faster, more accurate, and semantically aware results.&lt;/p&gt;</description>
      </item>
    <item>
        <title>Introducing Terraform Support for PGVecto.rs Cloud</title>
        <link>https://vchord.pgsty.com/blog/post/introducing-terraform-support-for-pgvectors-cloud/</link>
        <pubDate>Wed, 24 Jul 2024 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/introducing-terraform-support-for-pgvectors-cloud/</guid>
        <description>&lt;p&gt;We are thrilled to announce the release of our &lt;a href=&#34;https://registry.terraform.io/providers/tensorchord/pgvecto-rs-cloud/latest&#34;&gt;Terraform provider for PGVecto.rs Cloud&lt;/a&gt;. This new provider is designed to simplify the process of managing resources on our &lt;a href=&#34;https://vchord.pgsty.com/cloud/&#34;&gt;cloud service&lt;/a&gt;, providing users with an intuitive and streamlined experience for managing their Postgres cluster setup and operation through infrastructure as a code tool — &lt;strong&gt;Terraform&lt;/strong&gt;. For those unfamiliar with &lt;a href=&#34;https://www.terraform.io/&#34;&gt;Terraform&lt;/a&gt;, it is an open-source tool for building, changing, and versioning infrastructure safely and efficiently. It enables users to define their infrastructure as code, allowing them to provision and manage resources programmatically.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
