What changed
PGX announced pgx-bm25 1.0 on October 7, 2026. It installs as the bm25_native extension and adds USING bm25_native to index text for Okapi BM25 relevance-ranked search. It implements an ordered index scan for ORDER BY relevance with LIMIT, avoiding a separate Sort step in supported plans. Its index data lives in ordinary PostgreSQL index pages and uses PostgreSQL WAL, crash recovery and physical replication. Version 1.0 supports PostgreSQL 17 and 18, with 19 beta tested but not yet supported.
Why it matters
Small teams building internal search, document retrieval or text-heavy SaaS features may be able to get relevance-ranked full-text results from an existing PostgreSQL cluster instead of deploying and synchronising another search engine. This is a third-party C extension, not a PostgreSQL core feature; operator choice depends on ranking quality, query shapes, hosted-database extension permissions and index maintenance trade-offs.
What 1.0 actually adds
Create the bm25_native extension, build an index with USING bm25_native (body), then use @@@ to match text and ORDER BY body &@@ 'query' to retrieve relevance-ranked results. PGX says ordered index scans can return top-k results without a separate sorting stage. The index uses PostgreSQL's WAL and replication mechanisms rather than maintaining an external search service.
What it does not replace
It does not make PostgreSQL's built-in tsvector search obsolete and is not a drop-in replacement for every Lucene, Meilisearch or Elasticsearch workload. It needs PostgreSQL 17 or 18 and server development headers for installation. Managed Postgres platforms that do not allow custom C extensions may not support it.
Planner and row-level-security caveats
The project README warns that its match operator can behave differently if evaluated as a filter rather than through its index, including when row-level security applies or an OR expression prevents index use. Some field-scoped queries then raise feature_not_supported instead of silently changing semantics. It currently lacks bitmap index scan support. Teams relying on RLS or complex query plans should test actual plans and results before production use.
Evidence and scope
The October 7 PostgreSQL announcement and the maintained source repository establish the release, installation interface and architectural claims. Independent technology coverage confirms the release, but public performance comparisons remain primarily project-authored; no broad independent latency, recall or concurrency validation was established in this pass.