realZachi/pg-jev

选用指南

AI 根据 README 整理 · 2026/10/14 14:26:08

使用方式

通过 SQL 函数使用，如 jev()、jev_prob() 等，可集成到现有查询中。

查看 README 依据

[TypeSafe's Jev](https://docs.typesafe.ai), a System One model that returns calibrated probabilities instead of generated text. No index, no embeddings, no vector column. Website: [pgjev.com](https://pgjev.com) ```sql CREATE EXTENSION jev CASCADE; SELECT * FROM people WHERE jev(people, 'the name is European'); SELECT subject, jev_prob(tickets, 'the customer is angry') AS p FROM tickets ORDER BY p DESC LIMIT 20; SELECT jev_choice(tickets, 'which team should handle this?', ARRAY['billing', 'technical', 'security', 'sales']) AS team, count(*) FROM tickets GROUP BY 1;

部署要求

需要 PostgreSQL 14–17 并安装 plpython3u，需要超级用户权限和 TypeSafe API 密钥。

查看 README 依据

made no difference at 20. Naming rows instead of indexing them did not help. Batches of 20 cost 4 % more tokens than batches of 40 and are just as fast, because a request's latency barely depends on its size. ## Install Requirements: PostgreSQL 14–17 with `plpython3u` (package `postgresql-plpython3-NN` on Debian/Ubuntu, included in the EDB and Postgres.app builds), a superuser, and a TypeSafe API key from https://console.typesafe.ai. Managed hosts that withhold superuser or `plpython3u` (Supabase, Neon, RDS, …) cannot run it; see

已知限制

全表扫描设计，每行数据会发送到第三方 API，不适合敏感数据；plpython3u 为不受信任语言，仅超级用户可创建扩展。

查看 README 依据

- Send only the columns the judgment needs: create a view with the relevant columns (and any pre-filter) and call `jev(view_alias, ...)` on the view. Views are read ahead and batched like tables. ## Caveats - This is a full scan by design: every row the executor asks about goes to the API. Cheaper predicates in the same `WHERE` run first and their rejects are skipped; a `LIMIT` stops early; `jev.max_rows_per_statement` caps spend. - Row contents are sent to a third-party API. Do not use it on data you may not share.

- The answer cache lives in the backend session (PL/Python `GD`) and can grow with unique row/question pairs; `jev.max_prefetch_rows` does not cap it. `jev_cache_clear()` clears cached answers and read-ahead state for the current session, and ending the backend session releases the cache. Connection pools with many sessions each warm their own cache. - `plpython3u` is an untrusted language: only superusers can create the extension, and functions run with the server's OS privileges. ## Development ```bash