Another insane Jev use case!
@_avichawla80K followers
301,592 views
33 Comments
Comments from the original post on X (Twitter)

@TechSoulGeeta
Nice demo. A few practical details from the pg-jev docs and measurements that are worth knowing before trying this on real data: On a 2,000-row table the cold first pass took about 3.5 s and ~$0.012 (≈296k input tokens). The same condition from the session cache dropped to ~50 ms, and a fresh condition with LIMIT 3 finished in ~0.6 s because the read-ahead can stop early. Batches are capped at 20 rows; ground-truth checks showed 100 % agreement up to that size and a clear drop past ~25–40. It is a full scan of whatever the executor still asks about, so cheaper predicates in the same WHERE (age > 40 AND jev(…)) prune rows before they are sent. Requires Postgres 14–17 with plpython3u and superuser privileges, so managed hosts (Supabase, Neon, RDS, etc.) cannot run it. Row contents go to the TypeSafe API.
3 likes

@eandualem
Checked out the repo, really interesting idea! Could see an LLM turning “how many users liked our latest changes?” into SQL with Jev calls to classify their feedback and count the results. I’ve been using Jev in Entune to pick suitable dictionary replacements for dictation instead of blindly replacing words. Fun to see it used inside Postgres too.
2 likes

@nisten
i read it as peg jev
1 like

@hexablob
I like this for exploring data, but I'd keep a model outage away from customer-facing queries. Would you materialize the labels for production, or run Jev live in WHERE?
1 like

@NeelakandanNC
jev seem to have wider use cases than llm due to its narrowness, speed and cost
1 like

@Discerner4u
The Ganesha logo is cool and also apt :) Nice one
1 like

@jeheskielsunloy
ngl keeping semantic classification directly inside the sql planner instead of pulling rows into python memory is so clean
1 like

@BraaiEngineer
Batching affects probability

@singularity_bly
I’d compare those topic and relevance decisions with GLiDE. It beats Jev on Decision Index retrieval, 60.9 vs 55.4, and overall, 64.81 vs 57.91. Would be interesting to see which Hacker News rows the two models disagree on.

@GNUmanth
/me was baking

@proxy_vector
Does the semantic filter call the model once per row at query time?

@FReza1984
Local decision engines show how language models can power deterministic database workflows.

@GanjaRedNight
told my boss i'd never have to learn sql and was right again.

@chlozuzzix
asking postgres questions in plain english is the only way db work should feel. every other extension sells me a vector index and calls it a day

@Leon_Vandenberg
@garrytan Gbrain might use this?

@LeaT_Design
so you just bolted an llm onto the query planner and called it a feature. where's the cost breakdown for real traffic though, that video shows a demo not a bill

@crypto_ninjas
Semantic search is the real game-changer here. It’s not just about keywords anymore—understanding intent and context is what makes Jev so powerful.

@emanatedMo
I literally put a plan to build a jev based postgres linter and verifier yesterday, thanks for sharing!

@gitshipdone
peg jev... need a NSFW spoiler plz

@yohakujpn
something new on Jev ecosystem













