<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>contextual-retrieval on Vchord</title>
    <link>https://vchord.pgsty.com/tags/contextual-retrieval/</link>
    <description>Recent content in contextual-retrieval on Vchord</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    
    
    
      <lastBuildDate>Mon, 02 Nov 2026 19:35:19 +0800</lastBuildDate>
    
    
      <atom:link href="https://vchord.pgsty.com/tags/contextual-retrieval/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Optimize RAG with Contextual Retrieval in PostgreSQL</title>
        <link>https://vchord.pgsty.com/blog/post/optimize-rag-with-contextual-retrieval-in-postgresql/</link>
        <pubDate>Fri, 30 May 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/optimize-rag-with-contextual-retrieval-in-postgresql/</guid>
        <description>&lt;p&gt;In the standard approach to Retrieval Augmented Generation (RAG), a common practice is to break down large documents into smaller, more manageable chunks. This is primarily done to improve the efficiency of the retrieval process, leveraging the sentence embedding and keyword bm25 scoring, allowing systems to quickly find and pull relevant pieces of information. While effective in many scenarios, this method can introduce a significant challenge: the potential for individual chunks to lose their surrounding context.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
