jev

jev : Natural-language row filtering, ranking and classification through a Jev-compatible API

Overview

Packages

Source

pig build pkg jev;		# build rpm/deb

Install

Make sure PGDG and PIGSTY repo available:

pig repo add pgsql -u   # add both repo and update cache

Install this extension with pig:

pig install jev;		# install via package name, for the active PG version

pig install jev -v 17;   # install for PG 17
pig install jev -v 16;   # install for PG 16
pig install jev -v 15;   # install for PG 15
pig install jev -v 14;   # install for PG 14

Create this extension with:

CREATE EXTENSION jev CASCADE; -- requires plpython3u

Usage

Sources:

• README.md
• CHANGELOG.md
• sql/jev–0.2.0–0.2.1.sql
• PGXN 0.2.1

jev filters, ranks and classifies rows using natural-language conditions evaluated by a configured Jev-compatible API. It requires plpython3u, superuser installation; TypeSafe-hosted endpoints also require an API key. The upstream documented PostgreSQL range is 14–17; no preload is needed.

Query rows

CREATE EXTENSION jev CASCADE;
SET jev.api_key = 'your-key';
CREATE TABLE jev_demo (id integer, body text);
INSERT INTO jev_demo VALUES (1, 'The customer requests a refund');
SELECT id, jev_prob(jev_demo, 'the customer requests a refund')
FROM jev_demo;
SELECT jev_stats();

jev() returns a boolean predicate; jev_prob() returns a probability. jev_choice() classifies among options, and jev_score() evaluates ordered levels. Cache and connection pools are session-local; jev_cache_clear() clears session state.

Service and data boundaries

Row contents are transmitted to the configured API. Set jev.api_url for the intended service and use jev.max_rows_per_statement and jev.max_chars_per_statement to cap work. API latency and charges depend on the service and data volume. The API key must be handled as a credential.

PL/Python runs with server operating-system privileges. Hosts that withhold superuser access or PL/Python cannot run this extension. Local package tests use the upstream mock API; they do not validate the remote model’s judgment quality.

0.2.1 Endpoints

In 0.2.1, jev.api_key is required only for *.typesafe.ai hosts. For a locally operated or other compatible endpoint, unset keys omit the Authorization header; a configured key is still sent. Set jev.api_url to the intended trusted service. Install the matching files and run ALTER EXTENSION jev UPDATE for 0.2.0 databases. Model accuracy and data-handling policy still depend on the chosen service.