pg-jev - Jev judgements as SQL functions
What the pg-jev extension does - SQL functions that send each row to TypeSafe's Jev model and return a boolean, probability, score or class - how it batches and caches API calls, what it costs per row, and where it must not be used.
Read- AIpg-jev - Jev judgements as SQL functions
- DatabasesPostgreSQL 19 - what changes and what breaks
- DatabasesPostgreSQL 19 asynchronous I/O - worker autoscaling and read-ahead
- DatabasesPostgreSQL 19 autovacuum - parallel workers and the scoring system
- AIAgent harnesses - the layer that owns the loop
- AIAgent sandboxes - where unvetted code runs
- Data EngineeringApache Spark
- Data EngineeringChange data capture
Explore by area
No technology stands alone.
Start with one technology. Explore its dependencies, companion tools and alternatives without losing your place.
Direct connections
Dependency
Recorded use
Complements
Alternatives
No outgoing connections recorded. This does not mean that none exist.
Connections are editorial associations, not live traffic.
How to read this map
Only the selected technology's outgoing records are shown. Read each group from the selected technology to its named connections. Reverse and indirect relationships are not inferred.
- Dependency
- Listed dependencies need guide-specific scope; they are not universal requirements.
- Recorded use
- A usedBy entry is not turned into a dependency claim about the referenced technology.
- Complements
- Tools recorded as working alongside one another do not have to be deployed together.
- Alternatives
- Alternatives are comparisons, not guaranteed drop-in replacements.
Focus a connection for its category and exact direction. Activate its name to inspect it here; Guide or Profile opens a reading destination. Back returns to your previous selection. Escape closes the preview. Lines connect the selected technology to its relationship groups; the brief selection pulse is emphasis, not live traffic.
Learn it properly
Outcomes stated as capabilities you can test, with prerequisites that link to what they assume.
A staged path from modelling a domain in tables to evolving a live schema under traffic, covering normalisation, storage internals, index design, the query planner, transactions and migrations, with a verifiable capability at each stage.
intermediateAI EngineeringA staged path from using an LLM API correctly to shipping an evaluated, guard-railed RAG or agent system, with a verifiable capability per stage.
advancedProduction InfrastructureA staged path from Linux fundamentals to running highly available, observable services on Kubernetes, with a verifiable capability at each stage.
intermediateClaude and Anthropic toolingA staged path through the Messages API, tool use, Claude-specific evaluation, MCP, Claude Code permissions, and production cost, latency and failure.
intermediateBuilding Agents with LangChain and LangGraphA runnable document-assistant course covering model interfaces, reducers, retrieval evaluation, bounded delegation and persistent approval, with an offline lab and an interactive state diagram.
Use it, do not just read it.
Three ways to interrogate the material instead of reading it linearly.
What is happening now
All updates- Planet PostgreSQLChristophe Pettus: Portions Copyright
- Planet PostgreSQLSHRIDHAR KHANAL: The Database Restarted Without Restarting: The Basics of PostgreSQL Signals (Part 1)
- Planet PostgreSQLRadim Marek: Postgres relation files, filed under base/
- Planet PostgreSQLPeter Eisentraut: The reverts will continue until morale improves
- Planet PostgreSQLChristophe Pettus: All Your GUCs in a Row: array_nulls (Special Update)
- Planet PostgreSQLHollis Varden: Five PostgreSQL queries that did more work than I asked for