Angaben zum Datum
Datum aus der Quelle.
Erstmals gesehen am .
pgx-bm25 1.0: BM25-Volltextsuche als nativer PostgreSQL-Index
PGX Inc. veröffentlicht pgx-bm25 1.0, eine Erweiterung für PostgreSQL 17 und 18, die Okapi-BM25-Volltextsuche mit Relevanzsortierung als nativen Index (bm25_native) mit WAL-Logging, VACUUM-Unterstützung und Snowball-Wörterbüchern bereitstellt.
PGX Inc. has released version 1.0 of pgx-bm25, an extension that adds Okapi BM25 ranked full-text search to PostgreSQL as a native index access method. It supports PostgreSQL 17 and 18, and installs as bm25_native.
CREATE EXTENSION bm25_native;
CREATE INDEX docs_bm25 ON docs USING bm25_native (body);
SELECT id, bm25_score(ctid) AS score
FROM docs
WHERE body @@@ 'quick fox'
ORDER BY body &@@ 'quick fox'
LIMIT 10;
@@@ selects the matching rows and &@@ orders them by relevance. The query runs as an ordered index scan; there is no Sort node.
It is a PostgreSQL index
The whole index lives in the index relation's own pages, so it gets WAL logging, crash recovery, and physical replication from core. VACUUM maintains it. There is no external search engine and no separate runtime to operate. The extension is written in C against the stock server headers and builds with PGXS; a C compiler and pg_config are the whole toolchain.
Text is analyzed with PostgreSQL's own Snowball dictionaries, with the language set per index, so a search for negligent finds negligence. Ranked top-N queries use block-max WAND, so a typical LIMIT 10 search does not have to score every matching document.