<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Announcement | Lakebase Search: State-of-the-art full-text and vector search for Postgres in Lakebase Articles</title>
    <link>https://community.databricks.com/t5/lakebase-articles/announcement-lakebase-search-state-of-the-art-full-text-and/m-p/170728#M81</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Lakebase Postgres now includes built-in full-text and vector search, generally available on AWS and Azure. With &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_vector&lt;/SPAN&gt;&lt;SPAN&gt; for approximate nearest-neighbor search and &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_text&lt;/SPAN&gt;&lt;SPAN&gt; for BM25 search, teams can run semantic, keyword, and hybrid retrieval alongside operational data, without maintaining a separate search system and ETL pipeline.&lt;/SPAN&gt;&lt;/P&gt;
&lt;H2&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Key Highlights&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H2&gt;
&lt;UL&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Search directly in Postgres&lt;/STRONG&gt;&lt;SPAN&gt;: Combine vector similarity, BM25 keyword relevance, SQL filters, and joins against live operational tables in one database.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Built for scale&lt;/STRONG&gt;&lt;SPAN&gt;: Lakebase Search uses a serverless architecture that separates storage from compute, scales to zero when idle, and scales compute with query demand rather than data volume.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Designed for agent retrieval&lt;/STRONG&gt;&lt;SPAN&gt;: Support bursty, parallel retrieval workloads with usage-based scaling, low-latency queries, and governed access through standard database controls.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Efficient vector search&lt;/STRONG&gt;&lt;SPAN&gt;: &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_vector&lt;/SPAN&gt;&lt;SPAN&gt; uses hierarchical clustering and compact quantization to search only the relevant data while balancing recall and latency. The reported 100M-vector benchmark achieved 97% recall at 71 ms P99 latency.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Native hybrid search&lt;/STRONG&gt;&lt;SPAN&gt;: Combine &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_vector&lt;/SPAN&gt;&lt;SPAN&gt; and &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_text&lt;/SPAN&gt;&lt;SPAN&gt; to match both semantic meaning and exact keywords, useful for agent grounding and search experiences that need both signals.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Simpler operations&lt;/STRONG&gt;&lt;SPAN&gt;: Keep OLTP and search workloads together, with index builds designed to run in parallel and away from the primary database.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="p8i6j01 paragraph"&gt;&lt;A style="background-color: #ff3621; color: white; padding: 10px 20px; text-decoration: none; border-radius: 5px; font-weight: bold; display: inline-block;" href="https://www.databricks.com/blog/lakebase-search-state-art-full-text-and-vector-search-postgres?utm_source=bambu&amp;amp;utm_medium=social&amp;amp;utm_campaign=advocacy" target="_blank" rel="noopener"&gt; &lt;span class="lia-unicode-emoji" title=":backhand_index_pointing_right:"&gt;👉&lt;/span&gt; Read the full story here &lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Oct 2026 11:04:59 GMT</pubDate>
    <dc:creator>Tushar_Parekar</dc:creator>
    <dc:date>2026-10-06T11:04:59Z</dc:date>
    <item>
      <title>Announcement | Lakebase Search: State-of-the-art full-text and vector search for Postgres</title>
      <link>https://community.databricks.com/t5/lakebase-articles/announcement-lakebase-search-state-of-the-art-full-text-and/m-p/170728#M81</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Lakebase Postgres now includes built-in full-text and vector search, generally available on AWS and Azure. With &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_vector&lt;/SPAN&gt;&lt;SPAN&gt; for approximate nearest-neighbor search and &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_text&lt;/SPAN&gt;&lt;SPAN&gt; for BM25 search, teams can run semantic, keyword, and hybrid retrieval alongside operational data, without maintaining a separate search system and ETL pipeline.&lt;/SPAN&gt;&lt;/P&gt;
&lt;H2&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Key Highlights&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H2&gt;
&lt;UL&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Search directly in Postgres&lt;/STRONG&gt;&lt;SPAN&gt;: Combine vector similarity, BM25 keyword relevance, SQL filters, and joins against live operational tables in one database.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Built for scale&lt;/STRONG&gt;&lt;SPAN&gt;: Lakebase Search uses a serverless architecture that separates storage from compute, scales to zero when idle, and scales compute with query demand rather than data volume.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Designed for agent retrieval&lt;/STRONG&gt;&lt;SPAN&gt;: Support bursty, parallel retrieval workloads with usage-based scaling, low-latency queries, and governed access through standard database controls.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Efficient vector search&lt;/STRONG&gt;&lt;SPAN&gt;: &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_vector&lt;/SPAN&gt;&lt;SPAN&gt; uses hierarchical clustering and compact quantization to search only the relevant data while balancing recall and latency. The reported 100M-vector benchmark achieved 97% recall at 71 ms P99 latency.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Native hybrid search&lt;/STRONG&gt;&lt;SPAN&gt;: Combine &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_vector&lt;/SPAN&gt;&lt;SPAN&gt; and &lt;/SPAN&gt;&lt;SPAN&gt;lakebase_text&lt;/SPAN&gt;&lt;SPAN&gt; to match both semantic meaning and exact keywords, useful for agent grounding and search experiences that need both signals.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;STRONG&gt;Simpler operations&lt;/STRONG&gt;&lt;SPAN&gt;: Keep OLTP and search workloads together, with index builds designed to run in parallel and away from the primary database.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="p8i6j01 paragraph"&gt;&lt;A style="background-color: #ff3621; color: white; padding: 10px 20px; text-decoration: none; border-radius: 5px; font-weight: bold; display: inline-block;" href="https://www.databricks.com/blog/lakebase-search-state-art-full-text-and-vector-search-postgres?utm_source=bambu&amp;amp;utm_medium=social&amp;amp;utm_campaign=advocacy" target="_blank" rel="noopener"&gt; &lt;span class="lia-unicode-emoji" title=":backhand_index_pointing_right:"&gt;👉&lt;/span&gt; Read the full story here &lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2026 11:04:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-articles/announcement-lakebase-search-state-of-the-art-full-text-and/m-p/170728#M81</guid>
      <dc:creator>Tushar_Parekar</dc:creator>
      <dc:date>2026-10-06T11:04:59Z</dc:date>
    </item>
  </channel>
</rss>

