Sanderhoff-alt 0b6b5261a2 feat(pg_search): allow the extension function schema to be configured (#3759) ...

Managed PostgreSQL distributions install the pg_search functions (score, boolean,
match) under a schema of their choosing — pgsearch rather than paradedb on the
distribution in #3757 — so the hardcoded paradedb. qualification made the
pg_search backend unusable there without a custom image or wrapper functions.

Adds HINDSIGHT_API_TEXT_SEARCH_EXTENSION_PG_SEARCH_FUNCTION_SCHEMA (default
paradedb, validated as a plain PG identifier since it is interpolated into raw
SQL) and threads it through both builders that qualify those calls: the
memory-recall BM25 arm and the knowledge-pages arm. Index creation needs no
change — USING bm25(...) resolves the access method globally. The pdb tokenizer
pseudo-types stay fixed; they come from ParadeDB's own install DDL and are
independent of the extension's target schema.

Fixes #3757.

2026-08-31 11:18:39 +02:00

..

docker-compose.yaml

feat(pg_search): allow the extension function schema to be configured (#3759)

2026-08-31 11:18:39 +02:00

Dockerfile

feat(api): add ParadeDB pg_search as Citus-compatible BM25 backend (#1755)

2026-05-26 16:45:16 +02:00