<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>bm25 on Vchord</title>
    <link>https://vchord.pgsty.com/tags/bm25/</link>
    <description>Recent content in bm25 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/bm25/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>PostgreSQL Full-Text Search: Fast When Done Right (Debunking the Slow Myth)</title>
        <link>https://vchord.pgsty.com/blog/post/postgresql-full-text-search-fast-when-done-right-debunking-the-slow-myth/</link>
        <pubDate>Wed, 02 Apr 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/postgresql-full-text-search-fast-when-done-right-debunking-the-slow-myth/</guid>
        <description>&lt;p&gt;You might have come across discussions or blog posts suggesting that PostgreSQL&amp;rsquo;s built-in full-text search (FTS) struggles with performance compared to dedicated search engines or specialized extensions. A notable recent example comes from &lt;strong&gt;Neon&amp;rsquo;s blog post, &amp;ldquo;Performance Benchmark: pg_search on Neon&amp;rdquo;&lt;/strong&gt; (&lt;a href=&#34;https://neon.tech/blog/pgsearch-on-neon&#34;&gt;link&lt;/a&gt;).&lt;/p&gt;&#xA;&lt;p&gt;In their benchmark, Neon compared query performance on their database platform &lt;em&gt;with&lt;/em&gt; their &lt;code&gt;pg_search&lt;/code&gt; extension (based on Rust&amp;rsquo;s Tantivy library via &lt;code&gt;pgrx&lt;/code&gt;) against the Postgres built-in fulltext search setting with tsvector and GIN index. They commendably stated they optimized this standard setup by adding GIN indexes where appropriate (benchmark code available &lt;a href=&#34;https://github.com/paradedb/paradedb/tree/dev/benchmarks&#34;&gt;here&lt;/a&gt;).&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
