The same gate, with and without MCP running
One model (base Qwen3-8B, temperature 0), 13 tasks (6 everyday, 7 traps) and a superuser oracle that compares every table before and after each task. Only the connection changes: native (one SQL statement through pg_agent_gate), native-loop (the same, agentic), gated-mcp (the same gate over MCP) and stock-mcp (a popular Postgres MCP server with the same privileges and no gate). Reported per arm: good tasks done, trap breaches, prompt tokens, model calls, median seconds per task, errors.
Rerun: gh workflow run compare.yml -R <your-fork>/agent-gate-demo -f config=cited
- 13 tasks is a demonstration, not a statistical benchmark; repeat=3 shows run-to-run variation.
- The model server runs with a 4096-token context window. The MCP arms carry tool definitions and tool results inside it; in the cited run one gated-mcp error was a context overflow. A larger window would likely change the MCP arms' numbers.
- Times come only from clean GitHub runners; times from a shared machine are never cited.
- The cited run measured pg_agent_gate 0.4.0 on PostgreSQL 18; the public image ygg-pg 0.3.6 ships 0.4.3 on PostgreSQL 19rc2. config=current measures 0.4.3.
Runs
Red Hat container certification checks (preflight) on the public image running
Runs Red Hat's openshift-preflight `check container` against the published ygg-pg image, pulled by digest with no registry credential. Reported: checks passed, failed and errored. Passing preflight is a prerequisite for container certification; it is not the certification.
Rerun: preflight check container ghcr.io/latamflows/ygg-pg@sha256:ec1aabe4be95f2f84d9c06aa612edc6346079dc7ebfe93280332cd7905c0a9f1
- A pass says the image meets the automated checks; it says nothing about the extensions' behaviour.
Runs
pg_phasevec vs pgvector: recall and latency on the same data designed
recall@10 against the dataset's published ground truth, and per-query latency (p50, p99) and throughput, for pg_phasevec (find, find_ivf) and pgvector (HNSW, IVFFlat) on the same vectors, the same queries, the same PostgreSQL build and the same machine, swept over each index's search knob. See SPEC.md.
Rerun: make recall-phasevec DSN=postgresql://... DATASET=nytimes-256-angular
- Designed, not run yet: no figure from this benchmark is published.
Runs