pg_net

A PostgreSQL extension that enables asynchronous (non-blocking) HTTP/HTTPS requests with SQL

Runssource: GitHubhomepagePythonApache-2.0commit 5fb36dd982bc

Python, Apache-2.0 licensed. The project labels itself: http client, postgres, postgresql, postgresql extension, sql and supabase.

pg_net runs. An Argusic agent installed it in 35 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

PostgreSQL 16.4 with pg_net 0.20.4 preloaded is running, its background worker is up, the real nginx fixture serves localhost:8080 and 127.0.0.1:8888 with 200s, and the full 92-test pytest suite passes.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 60 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
60 / 100
cost of the verifying run
$0.24 (measured)
recorded runs
2
last tested
stars
379
forks
44
open issues
43
watchers
28
size
1 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing pg_net, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • partial-suite runs failed on leftover state (orphaned net schema, stale queue rows, pre-created pg_stat_statements/roles)10 minutes
  • nginx failed: unknown directive if/echo and missing PCRE/zlib8 minutes
  • make link failed: cannot find -lcurl (no curl dev package installed)5 minutes
  • postgres startup failed: could not access file pg_stat_statements4 minutes
  • pip install blocked by PEP 668 and psycopg import failed3 minutes
  • tests could not connect: default socket path not writable and roles missing3 minutes
Install time
35 minutes
Cold machine to finish
26 minutes
Errors hit and fixed
7 hit, 7 fixed with no human help
How the result was proved
pytest full suite exited 0 with '92 passed in 141.60s'; net.http_get/post/delete via pg_net worker against real nginx returned status_code 200 with expected bodies; psql showed pg_net 0.20.4 installed and 1 worker running; curl localhost:8080 returned 200
Model tokens used
1,017,775
Exact commit tested
5fb36dd982bc
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- Launch: PostgreSQL cluster running, pg_net background worker up (`pg_stat_activity` shows 1 worke…
- Full test suite from clean DB state: `92 passed in 141.60s`, exit 0.
- Real end-to-end behavior: `net.http_get` → status 200 body `?x=1`; `net.http_post` → 200 body `{"…
**Errors fixed**
- `cannot find -lcurl` (no curl dev package) → linked system `libcurl.so.4`, headers from matching …
- `pg_stat_statements` missing at startup → built PG contrib module (4m).
- pg_net worker `role "" does not exist` → removed invalid `pg_net.username=''` config (2m).
- PEP 668 + missing psycopg binary → venv with `psycopg[binary]` (3m).
- Test env plumbing (socket dir `/tmp`, `runner`/`postgres` roles) (3m).
- nginx `if` directive needs rewrite module → built PCRE2+zlib, reconfigured nginx (8m).
- Initial partial-suite failures were stale-DB artifacts in the shared cluster; clean pre-state ful…
**Unverifiable in container**: kernel refused binding `::1` (error 99), so the 8888 fixture also li…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 35 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.

Of the 5 http-client projects Argusic has installed and timed, pg_net was the 4th fastest to reach a running state, and 4 of 5 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.24
Argusic Runner1/3Did not run20.000.90

Topics (from GitHub)

http-clientpostgrespostgresqlpostgresql-extensionsqlsupabase

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/pg_net.svg)](https://argusic.com/subject/pg-net)

Questions

Does pg_net run?
Yes. pg_net runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test pg_net?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5fb36dd982bc. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test pg_net?
The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pg_net take to install?
35 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does pg_net need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pg_net?
7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does pg_net compare with the alternatives?
Of the 5 http-client projects Argusic has installed and timed, pg_net was the 4th fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for pg_net?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion