Files
multica/server/migrations/033_comment_search_index.up.sql
yushen a2a021a0dd fix(search): make pg_bigm migration graceful when extension unavailable
CI uses pgvector/pgvector:pg17 which doesn't ship pg_bigm. Wrap
CREATE EXTENSION and index creation in DO/EXCEPTION blocks so the
migration succeeds without pg_bigm — indexes are skipped and search
falls back to plain LIKE scans.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-09 14:00:03 +08:00

10 lines
322 B
SQL

-- GIN index on comment content for LIKE '%keyword%' queries (pg_bigm).
-- Only created when pg_bigm is installed.
DO $$
BEGIN
CREATE INDEX idx_comment_content_bigm ON comment USING gin (content gin_bigm_ops);
EXCEPTION WHEN OTHERS THEN
RAISE NOTICE 'skipping bigram index on comment (pg_bigm not installed)';
END
$$;