The test gate runs on PGLite. We should add a CI job that spins up real Postgres + pgvector (pgvector/pgvector:pg17), runs the full suite + leak-test + cross-leak-test against it, and publishes real benchmark numbers (recall, answer accuracy, p50/p95 latency).
Why: prove the PGLite to Postgres parity claim with numbers, and exercise RLS on a non-superuser role in CI.
Scope
The test gate runs on PGLite. We should add a CI job that spins up real Postgres + pgvector (
pgvector/pgvector:pg17), runs the full suite +leak-test+cross-leak-testagainst it, and publishes real benchmark numbers (recall, answer accuracy, p50/p95 latency).Why: prove the PGLite to Postgres parity claim with numbers, and exercise RLS on a non-superuser role in CI.
Scope